Without example code it is hard to optimize. First thing is too make sure you are using things like LEFT JOIN instead of simple JOIN. ... View more

What result are you currently getting for CDATE? That is likely to be OS dependent so we need to see what you have. The likely solution will involve some form of %sysfunc(inputn or inputc depending, with a date informat. That would be inside a %sysfunc(putn({long expression},date9.)0; ... View more

If part of the issue is that restarting HTML output has files going into an "active" folder that isn't the one you want this may be of help. The first part of the code gets the location of the WORK library as a good place to put temporary files. Then the ODS HTML PATH= restarts HTML output and places the temporary HTML files in that library. proc sql noprint; select trim(path) into :workpath from dictionary.libnames where libname='WORK'; quit; %let workpath=%trim(&workpath); ods html path="&workpath"; ... View more

MikeZdeb wrote: you could use the asterisks and dim function in the above, but unless you do something previous to the data step to figure out how many variables you are checking, you'll have to hard code the dimension of DF ... so why bother with the asterisks and dim function in your code ... array Am{*} m1-m11; array ADF{*} $ DF1-DF11; do j=1 to dim(AM); Use of the DIM() makes it easier to keep the code working if you change the size of the array. For example suppose some requests a similar logic based on biweekly periods. Once the variables are assigned/created you don't have to remember to adjust the boundary on the loop. If you get to multiple nested loops you can really appreciate that feature. ... View more

continuing from last post: Proc freq data=want; table involvement; weight wt; run; ... View more

Try adding an ALPHA= to the PROC statement with an alpha appropriate for the different confidence limit you would be interested in. The default is ALPHA=.05, so use ALPHA=.10 if you want 90% limits. This should affect all test and limits produced. ... View more

Some code for what you are trying to do might help. It sounds like you are looking for either MISSING or PRELOADFMT depending on what is missing and what you want to appear. ... View more

Do you by any chance have ZIP codes in the data? If so you might find the ZIPCITY function helpful. If not restricing a search in the SASHELP.ZIP code data set to your state(s) of interest and LIKE or SOUNDEX functions to get a consistent name may be possible. ... View more

Possibly more effecient in some situations: Proc sql;      Create table nodup as      select distinct *      from yourdataset; quit; ... View more

Try ORDER=DESCENDING on those percent lines. ... View more

If you have to use CSV you may want to see if there is an option that produces quote qualified text. That would put quotes around the data that contains commas as part of the field and can be worked around. ... View more

A kludge which works if numeric or character: rc = sum ( (v1 ne v2),(v1 ne v3),(v1 ne v4),(v1 ne v5)); rc will have the number of mismatches. This uses the behavior of SAS to return 1 for a true logical comparison and 0 for a false. Care needs to be exercised for missing or blanks. ... View more

I think you may not be getting some of your output because of the two DO UNTIL(LAST.ID); loops. With an explicit OUTPUT in the second one then that is the ONLY place SAS is outputting the data. You may want another OUTPUT in the first loop as well. I would guess that you might be looking for a: IF LAST.ID THEN OUTPUT; And you might want a RETAIN TOTAL N .; at the begining of your data step. ... View more

Once upon a time I had a loosely related project that involved placing lots of external data into a Word document. You don't mention if you are using Word or how the external tables are generated so this may not apply. One approach could be to use links in Word. If each of the SAS tables you need are exported to a separate file whose name does not change then a Word document could be made with instructions to LINK each one. If the external RTF tables have a similar behavior then linking to those as well as the SAS output may accomplish the task. Since the locations of the source documents and file names will in effect be hard coded in the links my approach with this method was to export / create all of the supporting documents to someplace that made sense. Then when all of the data was ready copy it into a specific source document folder that the Word document would look for them. Open the Word document, refresh all of the links, SAVE AS A NEW DOCUMENT then break all of the links and save again. Somewhat cumbersome but in lieu of manually pasting 40 odd charts and 120 paragraphs of conditional text for 50+ reports it made lots of sense. ... View more