9.1.3 to 9.29.1.3 to 9.2 (27 lines) From: vj <vijay_sas@HOTMAIL.COM> Re: 9.1.3 to 9.2 (20 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> Re: 9.1.3 to 9.2 (67 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: 9.1.3 to 9.2 (72 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> Re: 9.1.3 to 9.2 (90 lines) From: vj <vijay_sas@HOTMAIL.COM> =?windows-1252?Q?Need_help_with_stats=2E=2E=2ECan_anyone_explain_me_the_dif?= =?windows-1252?Q?ference_between_HSD=2C_Duncan=92s_and_Fisher=92s_LSD=3F=3F_=28in_an_?= =?windows-1252?Q?easy_understandable_way=29?==?windows-1252?Q?Need_help_with_stats=2E=2E=2ECan_anyone_explain_me_the_dif?= =?windows-1252?Q?ference_between_HSD=2C_Duncan=92s_and_Fisher=92s_LSD=3F=3F_=28in_an_?= =?windows-1252?Q?easy_understandable_way=29?= (35 lines) From: Nuria <patxarana@GMAIL.COM> A Data Manupulation Problem - Please help ( VERY URGENT)Re: A Data Manupulation Problem - Please help ( VERY URGENT) (126 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> A new 9.2 option for labeling your sessionA new 9.2 option for labeling your session (33 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> A question and a commentA question and a comment (14 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
=?windows-1252?Q?Need_help_with_stats=2E=2E=2ECan_anyone_explain_me_the_dif?= =?windows-1252?Q?ference_between_HSD=2C_Duncan=92s_and_Fisher=92s_LSD=3F=3F_=28in_an_?= =?windows-1252?Q?easy_understandable_way=29?==?windows-1252?Q?Need_help_with_stats=2E=2E=2ECan_anyone_explain_me_the_dif?= =?windows-1252?Q?ference_between_HSD=2C_Duncan=92s_and_Fisher=92s_LSD=3F=3F_=28in_an_?= =?windows-1252?Q?easy_understandable_way=29?= (35 lines) From: Nuria <patxarana@GMAIL.COM> A Data Manupulation Problem - Please help ( VERY URGENT)Re: A Data Manupulation Problem - Please help ( VERY URGENT) (126 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> A new 9.2 option for labeling your sessionA new 9.2 option for labeling your session (33 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> A question and a commentA question and a comment (14 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
A Data Manupulation Problem - Please help ( VERY URGENT)Re: A Data Manupulation Problem - Please help ( VERY URGENT) (126 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> A new 9.2 option for labeling your sessionA new 9.2 option for labeling your session (33 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> A question and a commentA question and a comment (14 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
A new 9.2 option for labeling your sessionA new 9.2 option for labeling your session (33 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> A question and a commentA question and a comment (14 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
A question and a commentA question and a comment (14 lines) From: Jonathan Goldberg <jgoldberg@BIOMEDSYS.COM> A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
A question on Call executeA question on Call execute (66 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (79 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: A question on Call execute (30 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (58 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: A question on Call execute (109 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (44 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (136 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: A question on Call execute (49 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (20 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Re: A question on Call execute (33 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: A question on Call execute (46 lines) From: Dirk Van Krunckelsven <dirk.vk@GMAIL.COM> Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Accessing GE Centricity using SASAccessing GE Centricity using SAS (15 lines) From: Kevin Viel <citam.sasl@GMAIL.COM> CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
CURL useCURL use (25 lines) From: Killer <kk.majji@GMAIL.COM> Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Can I use proc in data step?Can I use proc in data step? (13 lines) From: Tim, Choi <yschoikd@LIVE.CA> Re: Can I use proc in data step? (46 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Can I use proc in data step? (27 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (21 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (36 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (36 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (48 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Can I use proc in data step? (69 lines) From: Chris Brooks <Chris.Brooks@ONS.GOV.UK> Re: Can I use proc in data step? (47 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (57 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (72 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (20 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Re: Can I use proc in data step? (30 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (87 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (103 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (85 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (96 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (113 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (146 lines) From: Matthew Pettis <matt.pettis@THOMSONREUTERS.COM> Re: Can I use proc in data step? (133 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (186 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Can I use proc in data step? (200 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (135 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (24 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (44 lines) From: Bob LaRue <bjlarue@SBCGLOBAL.NET> Re: Can I use proc in data step? (75 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (80 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (99 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Can I use proc in data step? (941 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (62 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Can I use proc in data step? (92 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (85 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Can I use proc in data step? (68 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Can I use proc in data step? (105 lines) From: xlr82sas <xlr82sas@AOL.COM> Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing)Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (438 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (687 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (818 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (769 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (835 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (889 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (823 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Can I use proc in data step? (Here's an example of 38 Procs Being Submitted _AND_ Executed While the SUBMITing Data Step Is Still Executing) (877 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Case-control, oversampled, matched studyCase-control, oversampled, matched study (44 lines) From: Daniel <daniel.biostatistics@GMAIL.COM> Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Change specification of TUKEY?Change specification of TUKEY? (47 lines) From: i.h. <FountainpenZ@AOL.COM> Re: Change specification of TUKEY? (71 lines) From: Eli Y. Kling <Eli.Kling@GMAIL.COM> Re: Change specification of TUKEY? (78 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Change specification of TUKEY? (18 lines) From: i.h. <FountainpenZ@AOL.COM> Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Code Hash OptimisationCode Hash Optimisation (49 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Code Hash Optimisation (70 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Compute EDF & its %'sCompute EDF & its %'s (16 lines) From: OR Stats <stats112@GMAIL.COM> Re: Compute EDF & its %'s (25 lines) From: cboevey <cboevey@GMAIL.COM> Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Convert Date from charct into MMDDYY10 typeConvert Date from charct into MMDDYY10 type (45 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (54 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (65 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (74 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Convert Date from charct into MMDDYY10 type (86 lines) From: Melodyp <pearsonmelody@GMAIL.COM> Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Converting PC SAS to MainFrame using tagsetsConverting PC SAS to MainFrame using tagsets (16 lines) From: Austin_HSBC <mark.r.austin@US.HSBC.COM> Re: Converting PC SAS to MainFrame using tagsets (25 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Coupling and cohesion in SAS macrosCoupling and cohesion in SAS macros (48 lines) From: M N <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (74 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Coupling and cohesion in SAS macros (144 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (109 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Re: Coupling and cohesion in SAS macros (162 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Coupling and cohesion in SAS macros (45 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Coupling and cohesion in SAS macros (389 lines) From: xlr82sas <xlr82sas@AOL.COM> Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Create VariableCreate Variable (34 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Create Variable (59 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Create Variable (66 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Create Variable (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Create new data setsRe: Create new data sets (29 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Cumulative Sum its urgentRe: Cumulative Sum its urgent (50 lines) From: atulrill <atulrill@GMAIL.COM> Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Custom script for SAS/Connect from PC/SAS to UNIXCustom script for SAS/Connect from PC/SAS to UNIX (61 lines) From: Debbie Lawton <debra_l_lawton@UHC.COM> Re: Custom script for SAS/Connect from PC/SAS to UNIX (104 lines) From: Dave Steven <dcsteven@U.WASHINGTON.EDU> Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Date Function turns back/forward one monthDate Function turns back/forward one month (21 lines) From: OR Stats <stats112@GMAIL.COM> Re: Date Function turns back/forward one month (47 lines) From: Mark Miller <mdhmiller@GMAIL.COM> Re: Date Function turns back/forward one month (35 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Date Function turns back/forward one month (48 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (71 lines) From: Seth StJames <sethstjames@GMAIL.COM> Re: Date Function turns back/forward one month (95 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Date Function turns back/forward one month (109 lines) From: Seth StJames <sethstjames@GMAIL.COM> Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Date Type of MM-DD-YYYY and MM-YYDate Type of MM-DD-YYYY and MM-YY (23 lines) From: Ya Wei <pearsonmelody@GMAIL.COM> Re: Date Type of MM-DD-YYYY and MM-YY (53 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Delete SAS Temporary Folders... 9.2 Running really slowDelete SAS Temporary Folders... 9.2 Running really slow (20 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (32 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (47 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (62 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (72 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (97 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (193 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (88 lines) From: Kevin Myers <KevinMyers@AUSTIN.RR.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (227 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (244 lines) From: OR Stats <stats112@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (273 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Delete SAS Temporary Folders... 9.2 Running really slow (264 lines) From: Gerstle, John (CDC/CCID/NCHHSTP) <yzg9@CDC.GOV> Re: Delete SAS Temporary Folders... 9.2 Running really slow (34 lines) From: Lou <lpogoda@HOTMAIL.COM> Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Deleting columnsDeleting columns (13 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (52 lines) From: Paul Dorfman <sashole@BELLSOUTH.NET> Re: Deleting columns (40 lines) From: Nickname unavailable <stinaikar_2000@YAHOO.COM> Re: Deleting columns (80 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (78 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Deleting columns (85 lines) From: palapara <yanjiemaomao@GMAIL.COM> Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Do this. Don't do that. Can't you read the signs?Do this. Don't do that. Can't you read the signs? (27 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (53 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (65 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (44 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (87 lines) From: John Burton <jrburtonsaspro@GMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (123 lines) From: Philip Rack <PhilRack@MINEQUEST.COM> Re: Do this. Don't do that. Can't you read the signs? (51 lines) From: Paige Miller <paige.miller@KODAK.COM> Re: Do this. Don't do that. Can't you read the signs? (75 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Do this. Don't do that. Can't you read the signs? (92 lines) From: Richard Read Allen <peakstat@WISPERTEL.NET> Re: Do this. Don't do that. Can't you read the signs? (97 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Do this. Don't do that. Can't you read the signs? (58 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (77 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (26 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (25 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (20 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Do this. Don't do that. Can't you read the signs? (111 lines) From: Mary <mlhoward@AVALON.NET> Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Download data from google trends using SAS; how to login to Google via SSRe: Download data from google trends using SAS; how to login to Google via SS (52 lines) From: ilias koen <ilias.koen@IKOEN.ORG> ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNCERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (60 lines) From: Abdallah abouihia <abouihia@GMAIL.COM> Re: ERROR: %SYSCALL, %SYSFUNC, or %QSYSFUNC (58 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Efficient in using merge or proc sqlEfficient in using merge or proc sql (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Efficient in using merge or proc sql (24 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Empty Lines inside the data setEmpty Lines inside the data set (41 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Empty Lines inside the data set (59 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Empty Lines inside the data set (80 lines) From: cat.. <cat.b41@GMAIL.COM> Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Error Graph from PROC GLIMMIXError Graph from PROC GLIMMIX (15 lines) From: OR Stats <stats112@GMAIL.COM> Error Graph from PROC GLIMMIX (20 lines) From: OR Stats <stats112@GMAIL.COM> Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Execution error in NLMIXEDExecution error in NLMIXED (36 lines) From: Lei <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (119 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (26 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (220 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (38 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (50 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (8 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (123 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Execution error in NLMIXED (15 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (17 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (39 lines) From: Lewis Jordan <lewjord@UGA.EDU> Re: Execution error in NLMIXED (11 lines) From: Lei Yu <kiki886@GMAIL.COM> Re: Execution error in NLMIXED (23 lines) From: Lewis Jordan <lewjord@UGA.EDU> Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Explicitly select a specific permanent formatExplicitly select a specific permanent format (32 lines) From: Matt Nizol <mnizol.news@YAHOO.COM> Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Extract page titlesRe: Extract page titles (126 lines) From: Killer <kk.majji@GMAIL.COM> Extract page titles (32 lines) From: Killer <kk.majji@GMAIL.COM> Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Extracting a variableExtracting a variable (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Extracting a variable (28 lines) From: Terjeson, Mark <Mterjeson@RUSSELL.COM> Re: Extracting a variable (30 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Re: Extracting a variable (34 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Extracting a variable (23 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Extracting a variable (21 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
FW: Why doesn't this macro delete the empty dataset?FW: Why doesn't this macro delete the empty dataset? (129 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Gchart HistogramGchart Histogram (18 lines) From: J M <jasonm@UCLA.EDU> Re: Gchart Histogram (33 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Gchart Histogram (48 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: Gchart Histogram (46 lines) From: J M <jasonm@UCLA.EDU> Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Getting percentages on weighted data using Proc TabulateGetting percentages on weighted data using Proc Tabulate (47 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Re: Getting percentages on weighted data using Proc Tabulate (53 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Getting percentages on weighted data using Proc Tabulate (113 lines) From: Jenny Gutbezahl <Jenny.Gutbezahl@MOLECULAR.COM> Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Hardcoding a Pt (using &sysdate)Hardcoding a Pt (using &sysdate) (34 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: Hardcoding a Pt (using &sysdate) (65 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: Hardcoding a Pt (using &sysdate) (43 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Hello EveryoneHello Everyone (14 lines) From: Kelvenyang <zhiting.yang@GMAIL.COM> Re: Hello Everyone (49 lines) From: Michael Raithel <michaelraithel@WESTAT.COM> How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to calculate L95% and U95% CI LimitHow to calculate L95% and U95% CI Limit (32 lines) From: SAS_learner <proccontents@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (26 lines) From: shiva <shiva.saidala@GMAIL.COM> Re: How to calculate L95% and U95% CI Limit (72 lines) From: SAS_learner <proccontents@GMAIL.COM> How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to define cell width in proc report while creating a PDF file?How to define cell width in proc report while creating a PDF file? (23 lines) From: Peng, Lily <Lily.Peng@PHARMA.COM> Re: How to define cell width in proc report while creating a PDF file? (45 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to display the number more than 20 digits?How to display the number more than 20 digits? (27 lines) From: raccoonjin@gmail.com <raccoonjin@GMAIL.COM> Re: How to display the number more than 20 digits? (45 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: How to display the number more than 20 digits? (33 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: How to display the number more than 20 digits? (37 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to display the number more than 20 digits? (61 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to find the positions of a second occurrence of a characterRe: How to find the positions of a second occurrence of a character (61 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: How to find the positions of a second occurrence of a character (79 lines) From: cat.. <cat.b41@GMAIL.COM> How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to find the positions of a second occurrence of a character in a stringHow to find the positions of a second occurrence of a character in a string (46 lines) From: Jamil Ibrahim <jibrahim@ACADAFF.UMSMED.EDU> Re: How to find the positions of a second occurrence of a character in a string (48 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to find the positions of a second occurrence of a character in a string (62 lines) From: Joe Matise <snoopy369@GMAIL.COM> How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to increase the grapics output area to ensure graph is close to legend at the top?How to increase the grapics output area to ensure graph is close to legend at the top? (85 lines) From: chengu <subrahmanyam.stat@GMAIL.COM> Re: How to increase the grapics output area to ensure graph is close to legend at the top? (101 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to solve below senarioHow to solve below senario (58 lines) From: Shaik Hymad <hymadsk@GMAIL.COM> Re: How to solve below senario (73 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to solve below senario (23 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to sort EG Summary TablesRe: How to sort EG Summary Tables (89 lines) From: Daniel Fernández <fdezdan@GMAIL.COM> How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
How to test if a date value is on 31th December any yearHow to test if a date value is on 31th December any year (18 lines) From: Anaconda <rune@FASTLANE.NO> Re: How to test if a date value is on 31th December any year (43 lines) From: Abel DK <rasmusabel@GMAIL.COM> Re: How to test if a date value is on 31th December any year (43 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Re: How to test if a date value is on 31th December any year (46 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (55 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (60 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Re: How to test if a date value is on 31th December any year (77 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: How to test if a date value is on 31th December any year (84 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: How to test if a date value is on 31th December any year (110 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: How to test if a date value is on 31th December any year (167 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: How to test if a date value is on 31th December any year (179 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: How to test if a date value is on 31th December any year (213 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Importing files with wild cards and datestampImporting files with wild cards and datestamp (27 lines) From: Styrmir <styrmirg@GMAIL.COM> Re: Importing files with wild cards and datestamp (72 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Importing files with wild cards and datestamp (63 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Importing files with wild cards and datestamp (106 lines) From: Jack Clark <jclark@HILLTOP.UMBC.EDU> Re: Importing files with wild cards and datestamp (124 lines) From: Data _null_; <iebupdte@GMAIL.COM> Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Informat question.Informat question. (28 lines) From: Brian Wallace <brian_c_wallace@YAHOO.COM> Re: Informat question. (39 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Informat question. (43 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: Informat question. (55 lines) From: Lou <lpogoda@HOTMAIL.COM> Re: Informat question. (64 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Installing SAS/IML Studio 3.2Re: Installing SAS/IML Studio 3.2 (72 lines) From: Michael Friendly <friendly@YORKU.CA> Re: Installing SAS/IML Studio 3.2 (99 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Installing SAS/IML Studio 3.2 (43 lines) From: Jerry Davis <jwd@UGA.EDU> Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Is there anyways to dynamically change datatypes for allRe: Is there anyways to dynamically change datatypes for all (55 lines) From: xlr82sas <xlr82sas@AOL.COM> Re: Is there anyways to dynamically change datatypes for all (69 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all (179 lines) From: xlr82sas <xlr82sas@AOL.COM> Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Is there anyways to dynamically change datatypes for all variables?Is there anyways to dynamically change datatypes for all variables? (51 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (98 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (46 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (79 lines) From: toby dunn <tobydunn@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (11 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there anyways to dynamically change datatypes for all variables? (32 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: Is there anyways to dynamically change datatypes for all variables? (158 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Is there anyways to dynamically change datatypes for all variables? (107 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Is there function to replace '.' and space to Underscore ?Is there function to replace '.' and space to Underscore ? (16 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Is there function to replace '.' and space to Underscore ? (31 lines) From: Joe Matise <snoopy369@GMAIL.COM> Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Kate or other editor (linux)Re: Kate or other editor (linux) (12 lines) From: Adam <azcera@GMAIL.COM> Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Large Categorical Variables in NLMIXEDLarge Categorical Variables in NLMIXED (30 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: Large Categorical Variables in NLMIXED (58 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (102 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Large Categorical Variables in NLMIXED (116 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Re: Large Categorical Variables in NLMIXED (95 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: Large Categorical Variables in NLMIXED (101 lines) From: Ryan <Ryan.Andrew.Black@GMAIL.COM> Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Libname ODBCLibname ODBC (18 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname ODBC (22 lines) From: Michael <michaelnx@GMAIL.COM> Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Libname OLEDBLibname OLEDB (21 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (38 lines) From: Michael <michaelnx@GMAIL.COM> Re: Libname OLEDB (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Libname OLEDB (21 lines) From: BK <byronkirby@GMAIL.COM> Re: Libname OLEDB (32 lines) From: Savian <savian.net@GMAIL.COM> Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Limiting the observationsLimiting the observations (13 lines) From: msiddu2000 <msiddu2000@GMAIL.COM> Re: Limiting the observations (56 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Looped intnx codeLooped intnx code (79 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Re: Looped intnx code (116 lines) From: Richard DeVenezia <rdevenezia@GMAIL.COM> Re: Looped intnx code (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Looped intnx code (134 lines) From: Jimaldo <jimnixon1984@GOOGLEMAIL.COM> Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Lossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport datasetLossless data transfer to and from R for SUN 64bit (big endian systems) - Source code to crate SAS transport dataset (38 lines) From: xlr82sas <xlr82sas@AOL.COM> Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Low concordance in weighted sampleLow concordance in weighted sample (34 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> Re: Low concordance in weighted sample (109 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: Low concordance in weighted sample (158 lines) From: SUBSCRIBE SAS-L Hema <hema_dave15@YAHOO.COM> MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
MACRO to Import an EXCEL workbook to SAS but only with DDEMACRO to Import an EXCEL workbook to SAS but only with DDE (24 lines) From: Paparodopoulos Nikolaos <npaparodopoulos@COMMERCIALVALUE.GR> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (51 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (39 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (700 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (106 lines) From: Mary <mlhoward@AVALON.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (608 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (623 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (638 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (658 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (46 lines) From: Savian <savian.net@GMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (30 lines) From: RolandRB <rolandberry@HOTMAIL.COM> Re: MACRO to Import an EXCEL workbook to SAS but only with DDE (40 lines) From: Lou <lpogoda@HOTMAIL.COM> Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Macro error - "ERROR: A character operand was found in the %EVAL...."Macro error - "ERROR: A character operand was found in the %EVAL...." (61 lines) From: Abc Unha <abcunha@YAHOO.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (98 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (45 lines) From: Schwarz, Barry A <barry.a.schwarz@BOEING.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (79 lines) From: Joe Whitehurst <joewhitehurst@GMAIL.COM> Re: Macro error - "ERROR: A character operand was found in the %EVAL...." (132 lines) From: Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE> Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Macro variable resolve timing issueMacro variable resolve timing issue (110 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Macro variable resolve timing issue (115 lines) From: Sophia Tong <sophiDT@HOTMAIL.COM> Re: Macro variable resolve timing issue (120 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (153 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Re: Macro variable resolve timing issue (165 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: Macro variable resolve timing issue (136 lines) From: Chang Chung <chang_y_chung@HOTMAIL.COM> Re: Macro variable resolve timing issue (169 lines) From: Suhong Tong <sophidt@HOTMAIL.COM> Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Min valuesMin values (39 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (76 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: Min values (95 lines) From: Robin R High <rhigh@UNMC.EDU> Re: Min values (70 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (17 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (78 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (89 lines) From: Yu Zhang <zhangyu05@GMAIL.COM> Re: Min values (88 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: Min values (83 lines) From: yingtao <yingtaoliu@GMAIL.COM> Re: Min values (93 lines) From: Data _null_; <iebupdte@GMAIL.COM> More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
More efficient way of combining dataMore efficient way of combining data (43 lines) From: dave crimkey <d_crimkey@YAHOO.COM> Re: More efficient way of combining data (75 lines) From: Tony Yang <tonyyangsasl@GMAIL.COM> Re: More efficient way of combining data (100 lines) From: Nathaniel Wooding <nathaniel.wooding@DOM.COM> ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ODS HTML to XLS File SizeODS HTML to XLS File Size (40 lines) From: gram333@gmail.com <gram333@GMAIL.COM> Re: ODS HTML to XLS File Size (54 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: ODS HTML to XLS File Size (57 lines) From: Jack Hamilton <jfh@STANFORDALUMNI.ORG> Re: ODS HTML to XLS File Size (59 lines) From: Savian <savian.net@GMAIL.COM> ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ODS Layout QuestionODS Layout Question (98 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (120 lines) From: Ya Huang <ya.huang@AMYLIN.COM> Re: ODS Layout Question (130 lines) From: J M <jasonm@UCLA.EDU> Re: ODS Layout Question (171 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ODS PDF - Creating Two ColumnsODS PDF - Creating Two Columns (22 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF - Creating Two Columns (57 lines) From: Randy Herbison <RandyHerbison@WESTAT.COM> ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ODS PDF startpage=nowODS PDF startpage=now (43 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (56 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: ODS PDF startpage=now (79 lines) From: J M <jasonm@UCLA.EDU> Re: ODS PDF startpage=now (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
ODS excel output: additonal unwanted folder createdRe: ODS excel output: additonal unwanted folder created (18 lines) From: Roy, Pallabi <pallabi.roy@GOUCHER.EDU> Re: ODS excel output: additonal unwanted folder created (33 lines) From: Joe Matise <snoopy369@GMAIL.COM> OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
OT: for StatisticiansRe: OT: for Statisticians (69 lines) From: AnnMaria DeMars <ademars@USC.EDU> Re: OT: for Statisticians (85 lines) From: Mike Rhoads <RHOADSM1@WESTAT.COM> On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
On-Line SAS Training, August and Sept 2009On-Line SAS Training, August and Sept 2009 (42 lines) From: Sierra Information Services <sfbay0001@AOL.COM> Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Optimisation of programOptimisation of program (30 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Re: Optimisation of program (14 lines) From: ash007 <RamsamyAshley@GMAIL.COM> Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
Out of memory with Proc PanelOut of memory with Proc Panel (65 lines) From: BruceBrad <b.bradbury@UNSW.EDU.AU> PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
PROC CORR helpPROC CORR help (18 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC CORR help (45 lines) From: Data _null_; <iebupdte@GMAIL.COM> PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
PROC EXPORT creating extra rowPROC EXPORT creating extra row (71 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (81 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC EXPORT creating extra row (92 lines) From: Joe Matise <snoopy369@GMAIL.COM> Re: PROC EXPORT creating extra row (109 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (112 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC EXPORT creating extra row (124 lines) From: xlr82sas <xlr82sas@AOL.COM> PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
PROC ROBUSTREGPROC ROBUSTREG (42 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (57 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (99 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (81 lines) From: Dave Fournier <otter@OTTER-RSCH.COM> Re: PROC ROBUSTREG (21 lines) From: Peter Flom <peterflomconsulting@MINDSPRING.COM> Re: PROC ROBUSTREG (129 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (144 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (72 lines) From: paul wilson <paulwilsn@YAHOO.COM> Re: PROC ROBUSTREG (110 lines) From: Arthur Tabachneck <art297@NETSCAPE.NET> Re: PROC ROBUSTREG (74 lines) From: Dale McLerran <stringplayer_2@YAHOO.COM> Re: PROC ROBUSTREG (196 lines) From: Robin R High <rhigh@UNMC.EDU> PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
PROC SQL weirdnessPROC SQL weirdness (29 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (40 lines) From: Chris Jones <chrisj75@GMAIL.COM> Re: PROC SQL weirdness (48 lines) From: Pinux <xflotmas@GMAIL.COM> Re: PROC SQL weirdness (26 lines) From: Data _null_; <iebupdte@GMAIL.COM> Re: PROC SQL weirdness (82 lines) From: Sigurd Hermansen <HERMANS1@WESTAT.COM> Re: PROC SQL weirdness (61 lines) From: Lou <lpogoda@HOTMAIL.COM> PROC UNIVARIATE Second Class Variable in SAS 9.1.3
PROC UNIVARIATE Second Class Variable in SAS 9.1.3