I'm very much with Tom on this one. Not that it couldn't be done without RegEx - but RegEx is just so much more versatile to deal with such cases. data have;   infile datalines truncover;   input text $100.;   datalines; This is my program PROGRAM is mine Change PROgram multiprogram vs time sharing programmatic art ; run; data want;   set have;   output = prxchange('s/(p)rogram\b/$1rogramming/i',-1,text); run; ... View more

Hello Keen@SAS, You can merge weeks and visits into a new character variable having valies like 2_15 (week=2 visits=15) and plot them on x-axis vertically using VALUE=(ANGLE=90) in your AXIS satetment. Sincerely, SPR ... View more

I have never been very successful with the split= option. However repeating a justification option will cause the text to split. [pre] axis1 value = (t=1 j=c '11' j=c 'years' t=2 j=c '12' j=c 'years'); proc gplot data=sashelp.class; plot weight* age/haxis=axis1; run; quit; [/pre] ... View more

Here is one way to do it with gchart and annotate... --- %let name=anno002; filename odsout '.'; data foo; input barmid $ 1-1 subgr $ 3-3 value err; datalines; A x 10 2 A y 15 1.5 A z 7 1.1 C y 10 1.6 C x 11 2.2 C z 17 2.4 B x 3 1.5 B y 6 1.3 ; run; proc sort data=foo out=foo_anno; by barmid subgr; run; data foo_anno; set foo_anno; by barmid; xsys='2'; ysys='2'; when='a'; if first.barmid then y_base=0; y_base+value; midpoint=barmid; function='move'; y=y_base; output; function='draw'; y=y+err; output; xsys='7'; x=-1; output; x=+2; output; /* draw the 'T' across the top */ run; goptions device=png; ODS LISTING CLOSE; ODS HTML path=odsout body="&name..htm" style=sasweb; goptions gunit=pct htitle=4.5 ftitle="albany amt/bold" htext=3.0 ftext="albany amt"; axis1 label=none order=(0 to 50 by 10) minor=none offset=(0,0); axis2 label=none; proc gchart data=foo anno=foo_anno; vbar barmid / type=sum sumvar=value subgroup=subgr raxis=axis1 maxis=axis2 nolegend width=10 coutline=graycc des='' name="&name"; run; proc print data=foo_anno; run; quit; ODS HTML CLOSE; ODS LISTING; ... View more

seems very complicated! How should we recognise prepositions? Why have you not upgraded to SAS9? peterC ... View more

Depends on what it is you want check? If you have DMS SAS, you can run your data step in the data step debugger. Another option is to use put statement(s) to print the contents of your variables to the SAS log. /Linus ... View more

If you're running on a PC, and your sas is prior to v9.2, you can typically use any non-unicode font character you have installed on your PC (for example, font="symbol" '6d'x for the mu character). But having gone through several versions (v9, v9.1, v9.1.3, v9.2) I don't have v8.2 on my PC anymore, so I can't try it to make 100% sure this will work. (btw - I *really* recommend upgrading to v9.2! - you're missing out on a lot of nice new features!) Might be a good question for Tech Support, if nobody here can give a definitive answer! ... View more

Learner, Just in case you'd prefer not to leave SAS base you could use the following. It generates the macro variables and displays their values in the log. I haven't fully tested it but it should be good for any number of words in the string. Of course you can replace the TRIM/LEFT functions with the appropriate version 9 function. data a; string = 'base macros sql advance'; i=1; DO UNTIL(SCAN(string,i)=''); call symput('VAR'!!put(i,3. -L),SCAN(string,i)); i+1; END; DO j = 1 to (i-1); x = symget('var'!!put(j,3.-l)); putv = 'var'!!TRIM(put(j,3.-l))!!'='!!TRIM(LEFT(x)); put putv; END; RUN; Regards, BPD ... View more

Generally you would have someone else QC the data by writing their own programs independently of yours. If you do not come up with the same numbers you would want to confer and see where the difference occurs. You would also want someone to go through your listings and check that all the counts add up/look sensible. ... View more

Hi: Basically, PROC REPORT needs a GROUP or ORDER variable that represents the place where break processing should occur. So you can either create your own "fake" page break variable or you could use a BY statement (every BY group starts a new page) or you could use the obs= option, as shown in this forum posting: http://support.sas.com/forums/thread.jspa?messageID=15692㵌 (this person wanted to suppress page numbers on the first page of the report, but the same OBS= and FIRSTOBS= technique would also work for what you want. cynthia ... View more

I find questions of the type "I know how to do it in SQL but how do I do it in the data step" a bit strange. I use to ask myself the opposite question - how can I do it in SQL instead? I prefer SQL if performance and coding complexity is the same (or better in SQL). There are in my opinion two advantages by using SQL in such cases: - Non SAS experts can read and understand the code. - Running the code against non SAS data can exploit the possibilities of using the benefits in implicit SQL pass-thru, which in turn can increase performance. Regards, Linus ... View more

Read the following old paper starting just upon your message and plenty of examples Paper 194-25 Pruning the SASLOG – Digging into the Roots of NOTEs, WARNINGs, and ERRORs Andrew T. Kuligowski Can be founded at http://www2.sas.com/proceedings/sugi25/25/po/25p194.pdf HTH Andre ... View more

Hi: It means that somebody needs a one-time report. It could be anything: How many patients does doctor XYZ have? If doctor XYZ dropped out of the trial, what's the age distribution of the patients who are left? Who are the patients that had batch 12345 of the drug? If this hurricane hits Florida, how many doctors and patients are affected? These are not questions that you can program in advance, but a general knowledge of SAS procedures will help you satisfy these kinds of requests. I'm sure there are many other examples -- the thing is that these requests are not really predictable -- it could be anything -- that's why they're called "ad-hoc". cynthia ... View more

Hi: For a history of SQL from theory to implementation, see this site: http://en.wikipedia.org/wiki/SQL For information about how SAS conforms or deviates from the ANSI standard for SQL, see this web page: http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/a002473705.htm (quote below is the first section from the page) PROC SQL follows most of the guidelines set by the American National Standards Institute (ANSI) in its implementation of SQL. However, it is not fully compliant with the current ANSI Standard for SQL.(footnote 1) The SQL research project at SAS has focused primarily on the expressive power of SQL as a query language. Consequently, some of the database features of SQL have not yet been implemented in PROC SQL. cynthia ... View more

Hi: These links represent the first hit on each page using the following search strings (in Google): Search string: What are descriptive statistics http://www.socialresearchmethods.net/kb/statdesc.php Search string: What are summary statistics http://en.wikipedia.org/wiki/Summary_statistics Search string: SAS "descriptive statistics" http://www.ats.ucla.edu/STAT/sas/modules/descript.htm These links represent hits on support.sas.com, when searching with the strings descriptive statistics and summary statistics -- and then looking for the documentation on the procedures that showed up in the first set of hits: Proc FREQ documentation: http://support.sas.com/documentation/cdl/en/procstat/59629/HTML/default/procstat_freq_sect001.htm Proc UNIVARIATE documentation: http://support.sas.com/documentation/cdl/en/procstat/59629/HTML/default/procstat_univariate_sect003.htm Proc MEANS documentation: http://support.sas.com/documentation/cdl/en/proc/59565/HTML/default/means-overview.htm cynthia ... View more