OK. Thank you. ... View more

Hi: I'm not sure what you mean by "device". This title statement should work for any ODS output in a destination which supports styles and in a viewer that supports hyperlinks. So, for example, ODS HTML, ODS RTF and ODS PDF will all support the use of a URL or hyperlink in the title. However, ODS RTF, when opened in Microsoft Word will require that you CTRL+click the hyperlink to follow the link. Generally, folks who use a "device" are using SAS/GRAPH device-based procedures (such as GCHART and GPLOT). The issue here is that ODS ESCAPECHAR is not used in SAS/GRAPH output. So, if the title you show is meant to go on a graph and the SAS/GRAPH device is in control of the title, then you can't use ODS ESCAPECHAR for that title. Several ODS destinations (ODS HTML, ODS RTF) have the NOGTITLE, NOGFOOTNOTE options, which allow ODS to control the title (instead of SAS/GRAPH). If you use these options, then you could use ODS ESCAPECHAR in your SAS title and footnote. TAGSETS.TABLEEDITOR is an HTML-based destination. However, I do not know whether NOGTITLE and NOGFOOTNOTE are allowable options for TAGSETS.TABLEEDITOR when you use SAS/GRAPH. You would have to check the documentation or work with Tech Support on this question. cynthia ... View more

hreftarget="_blank" in the second style {} use should work. -- David Kelley, SAS ... View more

Hi The ANCHOR= option creates numbered NAME attributes that all start with the same prefix string...so IDX1,IDX2, IDX3 or PILOT1, PILOT2, or PILOT3. To do what you want to do (have each NAME attribute be a different city), you would need to move into the world of SAS Macro processing and in addition, investigate how to append content to an HTML file using the NO_TOP_MATTER and NO_BOTTOM_MATTER sub options. However since you can probably predict what by group will get which IDX#, do you really need this level of control??? Cynthia ... View more

The OP must be using SAS 9.2 because of the SET statement and using the hyphen for a consecutive file-range specification. Additionally, some other options are using the OPTIONS setting NODSNFERR to convert the error to a warning message. And, with SAS 9.2, the file-prefix in the SET statement can be used with a trailing colon character. Scott Barry SBBWorks, Inc. ... View more

The following is a largely macro free alternative: /* an alternative to SAS Macro is to use a program that writes a program. This example uses a datasetp to write SAS program statements to a file, and then uses %include to include the program file just created and run it. You can use a "special" temporary SAS file if you use the TEMP destination, if you don't want the code to persist. (appropriate statement included as a comment) The advantage of a permanent file is you can debug what you have generated. For many applications this approach is easier to use and debug than SAS Macro, and you can see code generated in a text file, not just as a lot of disjointed text in the SAS Log */ filename tempcode "c:\notbackedup\testcode.sas"; /*filename tempcode TEMP;*/ data _null_; file tempcode; do i = 1 to 5; put 'filename in "C:\Documents and Settings\P000' i 1. ".dta;"; put "proc import datafile=in out=my_" i 1. " dbms = stata replace;"; put "run;"; end; run; %include tempcode ... View more

Since you have a 'color' variable, I assume you're annotating markers/dots on a gmap? If you annotate markers on a map, then you also have to annotate the color legend on the map - there's nothing built-in/automated to do it when you're using annotate. ... View more

This worked well. Thank you. ... View more

Hi: Are you doing something for SAS/GRAPH?? If so, this example may be useful: http://support.sas.com/documentation/cdl/en/graphref/61884/HTML/default/gr08ods2-ex.htm Modifying the code example a bit using SASHELP.CLASS, I can make the #IDX number use a dataset variable as shown below. Usage-wise, I'm not sure that the "target=_blank" is going to be OK, depending on where/how you plan to use this variable value. Usually, for ODS HTML output, you use the HREFTARGET style attribute to set TARGET=_BLANK: http://support.sas.com/kb/24/058.html If you have questions about creating hyperlinks with ODS and/or with SAS/GRAPH, you might wish to open a track with Tech Support. cynthia [pre] data testit; length namedrill $70; set sashelp.class; keep name namedrill; count+1; namedrill=catt('HREF=','"','http://test.com/zipinfo.html#IDX',left(put(count,2.0)),' target=_blank','"'); run; proc print data=testit; run; [/pre] Produces: [pre] Obs namedrill Name 1 HREF="http://test.com/zipinfo.html#IDX1 target=_blank" Alfred 2 HREF="http://test.com/zipinfo.html#IDX2 target=_blank" Alice 3 HREF="http://test.com/zipinfo.html#IDX3 target=_blank" Barbara 4 HREF="http://test.com/zipinfo.html#IDX4 target=_blank" Carol 5 HREF="http://test.com/zipinfo.html#IDX5 target=_blank" Henry 6 HREF="http://test.com/zipinfo.html#IDX6 target=_blank" James 7 HREF="http://test.com/zipinfo.html#IDX7 target=_blank" Jane 8 HREF="http://test.com/zipinfo.html#IDX8 target=_blank" Janet 9 HREF="http://test.com/zipinfo.html#IDX9 target=_blank" Jeffrey 10 HREF="http://test.com/zipinfo.html#IDX10 target=_blank" John 11 HREF="http://test.com/zipinfo.html#IDX11 target=_blank" Joyce 12 HREF="http://test.com/zipinfo.html#IDX12 target=_blank" Judy 13 HREF="http://test.com/zipinfo.html#IDX13 target=_blank" Louise 14 HREF="http://test.com/zipinfo.html#IDX14 target=_blank" Mary 15 HREF="http://test.com/zipinfo.html#IDX15 target=_blank" Philip 16 HREF="http://test.com/zipinfo.html#IDX16 target=_blank" Robert 17 HREF="http://test.com/zipinfo.html#IDX17 target=_blank" Ronald 18 HREF="http://test.com/zipinfo.html#IDX18 target=_blank" Thomas 19 HREF="http://test.com/zipinfo.html#IDX19 target=_blank" William [/pre] ... View more

Thank you. Looks good. ... View more

Hey Gunter, If the goal is to increase the graph resolution, use the IMAGE_DPI option on the ODS destination statement (for PRINTER or PDF, use the DPI option). If you are trying to do this with HTML output, I have found that browsers do not typically handle images higher than 100dpi very well. Let me know if this works out for you. Thanks! Dan ... View more

and if your data were too huge for that cartesian join, you could use proc MEANS to get grand, followed by class totals, and digest that summary:[pre] proc means noprint data= huge_data ; class job ; var count hours ; output sum= ; run ; data digested ; set ; retain g1-g2 ; if _type_ = 0 then do; g1= count ; g2= hours ; delete ; end ; count1 = g1 - count ; hours1 = g2 - hours ; keep job count1 hours1 ; run ;[/pre] Of course, huge is not specific, but I think the cartesian join in SQL will run out of resources before proc MEANS. any bets? PeterC ... View more

And also, if you're using the subgroup= so that the bars have multiple segments, you can control those colors using multiple pattern statements, such as: pattern1 v=solid color=pink; pattern2 v=solid color=blue; etc And, if you don't specify a color, then the ods style that's being used controls the color, which is another way to control it. ... View more

Hi Cynthia, You are right, I never notice the function of the "Column" statement. After adding it, the output is correct. Thanks, and sorry for bringing up the old discussion. ... View more

Where is your name="bmi" option??? The link between the KEYLEGEND and the plot statement is the fact that you use the name= name(s) on the plot statement and on the keylegend statement. A KEYLEGEND statement has to be "linked" in this manner. cynthia ... View more