About ballardw

ballardw · ‎10-27-2011

Also KEEPN may help on the ODS RTF statement.

ballardw · ‎10-27-2011

Put all of the characters to compress within one set of quotes. The comma between them as you have is trying to interpret the # as a modifier. street=upcase(compress(street,'.#');

ballardw · ‎10-25-2011

If I understand what you want to do the easiest may be a BY group process. Proc sort data=Sales out=SortedSales;by username;run; proc print data=SortedSales; by username; var sales_id sales_date price; run;

ballardw · ‎10-24-2011

I think you are at a point where you need to show exactly what your desired output is not what you have currently done.

ballardw · ‎10-21-2011

If you are wanting the tabular appearance one approach is to use the EXCELXP tagset. ods tagsets.excelxp file='output path\your file name.xml' ; <your proc tabulate code here> ods tagsets.excelxp; Then use EXCEL to open the resulting XML file.

ballardw · ‎10-18-2011

Which data step is not finishing? Since you have 3 data steps run just one at a time to see which what may be going on as a first step. By any chance have you upgraded to a newer version of Office? The path to Excel would have changed.

ballardw · ‎10-14-2011

I also suggest that routinely ending your macro variable calls with the period is not best practice. You may run into hard to diagnose issues if you get involved with complex macro resolution.

ballardw · ‎10-12-2011

I had experimented with TAGSETS.RTF and the TABLES_OFF='usertext' option in 9.2.0 and wasn't happy with the results. I now have 9.2.3 and I don't see any different behavior. Here is one example of a line of the text we are currently using: ods rtf text="^S={fontsize=26PT just=C fontweight=Bold leftmargin=1.0in rightmargin=1.0in topmargin=2in}{Nutrition Surveillance Trend Report}^{newline 5}{&yearstring}^{newline 2}{Idaho WIC Program}^{nbspace}"; When trying to use this with ODS TAGSETS.RTF TEXT= the justification and margin information is completely ignored. If instead I try ODS TEXT= then elements such as the "{" and "}" as well as some of the RTF tags such as "\b" become visible in the document. I have done a moderate amount of searching on the SAS tech support site for TAGSETS.RTF and uses of ESCAPECHAR and while ODS RTF and ODS PDF have many examples of inline formatting I haven't found any except font size or weight that are similar to my example for ODS TAGSETS.RTF. So at this time I'm saying this is only partially answered.

ballardw · ‎10-07-2011

Doc@Duke wrote: Thanks Art. I realized that my question was not sufficiently precise. I was looking for ICD-9-CM and ICD-10-CM. Each country can extend extend it in different ways. The "-CM' version is for the US. (Canada and NZ adopted ICD-10 several years ago, so they are more mature than we are here. It's required for hospital billing in the US by 10/1/2013). I just received notice that supposedly we'll be using ICD-11 in 2015 as well.

ballardw · ‎10-07-2011

Has anyone discovered a way to place text in an RTF document using ODS RTF TEXT="Any text" that doesn't result in the text appearing in a cell/table when opened in Word? My users complain about copying blocks of text out of reports formated as tables.

ballardw · ‎10-04-2011

If the relative path you need is relative to the location of the currently executing SAS program I think you are looking for the automatic SAS variables SAS_EXECFILEPATH and SAS_EXECFILENAME. This requires the executing code to have been saved. The macro variable PATH should be %let a=%sysget(SAS_EXECFILEPATH); %let b=%sysget(SAS_EXECFILENAME); %let path= %sysfunc(tranwrd(&a,&b,'')); %put &path; The macro variable PATH should be ready to use as %include "&path.codefile.sas";

ballardw · ‎09-30-2011

Or if you want to open from the SAS Explorer edit the TABLE member OPEN code, or create a new entry with: VIEWTABLE %8b."%s".DATA mode=edit view=form depending on the length of your variable labels may want colheading=name as well. Mode=edit isn't needed unless you either want to edit or sort the data.

ballardw · ‎09-30-2011

I'm not sure if this is exactly what you are looking for but a KEYS entry of VT _LAST_ / formview; opens the last dataset created in formview mode of viewtable. I suspect that appropriate DM commands should work if you need it in code.

ballardw · ‎09-26-2011

Peter's solution is better than mine in that you won't reference any non-existant data sets. Mine was just to show one approach using an explicitly iterated %DO loop using the obvious pattern shown in the data set names.

ballardw · ‎09-23-2011

Since the %DO isn't allowed in open code you need a macro. The example below allows parameters to change the start and end year. It could be made more generic with a parameter for the base of the data set name as well. Pay attention to the positions of semicolons!. %macro dname(syr=,eyr=); data all; set %do yr=&syr %to &eyr; %do m=1 %to 12; %let m2= %sysfunc(putn(&m,z2.));/* this is to get the leading zeros*/ /* the %DO will not increment leading 0*/ data&yr.&m2 %end; %end; ;/* to close set statement*/ /* other code*/ run; %mend; /* how to use*/ %dname(syr=2009, eyr=2011);

Online Status	Offline
Date Last Visited	Sunday