Sorry, you mis interpreted.  You can block out code with /* */ and see what each bit is doing.  Its the debug process.  Can't say anything without the data as that drives half of it. ... View more

Suppose you have a process such that a variable at some point must not exceed a specific length, such as to be incorporated into an existing data base. And you have a data merge with a data set that has that variable exceeding that length. Do you really want an undocumented process to automatically increase the length of the variable so that the process fails, mysteriously, at a later point? Or results in other unacceptable data? ... View more

Are you using Proc Report? I have a report in which I dynamically add color to highlight data that is below a threshold.  I normally output as a PDF, but I just tried outputting it to RTF instead, and the colors were applied to the rtf file. I have modified my code to create an example: PROC REPORT DATA = DailyImport nowd split='/' style(report)=[frame=void rules=none] ;   column studentid testid DateTest testgrade ;   define studentid        / order 'StudentId'            format= 6. width=6 ;   define testid           / display 'Test Id'            format= 4.   width=4 ;   define DateTest         / display 'Test Date'          format=MMDDYY10. width=10 ;   define testgrade        / display 'Grade'              format=abc.  width=6 CENTER ;   define failure          / noprint ;   compute failure ;   if testgrade <= 2 then   CALL define (_row_, "style", "style=") ;   else if testgrade = 3 then   CALL define (_row_, "style", "style=") ;  *orange ;   endcomp ;   compute after studentid / style=[font_size=1pt background=cxf0f0f0] ;   *put a line of gray shading between students ;   line ' ' ;   endcomp ;   title1 "Student Grades" ;   title2 "Daily Load: &sysdate" ; run ; (p.s. I hope I didn't introduce any syntax errors in this code... no guarantees!) ... View more

I did not mean to switch the SPANROWS on and off, either completely off or on. However the problem is that the trick I mentioned in the original post does not worki if SPANROWS is on. I have edited my first post and attached a sample data and code for my issue, there I only get the "stairstep" report table no matter what I do. And in fact with the data I generated the spanrows does really odd things and somehow makes some across values disappear. The problem is I can't post the actual data here, and it is really hard to mimic it. But basically with that data I would want to get all the order/group variables to show in every row and then get the table in "normal" form not in this stairstep formation which is really frustrating (somehow with the actual data I have managed to get the table to transpose it naturally, but couldn't get it working with the sample data...) ... View more

Well.  Firstly I would say that is a bad idea.  It make reviewing the table very difficult as you constantly need to scroll up to see what each column is.  My recommendation is to shrink the headers to a reasonable length, they are after all descriptives and need to be verbose.  So instead of: This column header was created on 12jun2014 using data derived from version 1 of the data and is the component. Use: Component With a footnote to explain it.  There are numerous techniques for this and different approaches. If you really need to do it, and are prepared for the backlash from the reviewer then: - Create a row in your dataset with the labels - Proc report the data, and set the labels to missing I wouldn't recommend it though. ... View more

HI,   Can you explain what you mean by "imagemap" feature? It doesn't matter whether you use PROC GCHART or PROC SGPLOT. When the destination is RTF, all the images are converted to internal RTF images. If you run this code, you should see that all the images are internal to the RTF file. To see this, you have to open the RTF file with Notepad and look for the {\*\shppict{\pict\emfblip sections. If you run the code below and open the resulting RTF file with Notepad, you will see 2 \shppict sections -- one for each graphic image. Starting with SAS 9.2, for both procedures, the style template in use determines most of the image characteristics. However, changes to each image can be made with the appropriate methods. You can always change the style template. Also, PROC SGPLOT uses either internal statement-level syntax for making color/font/etc changes or the ODS GRAPHICS statement and PROC GCHART uses internal statement-level syntax and the GOPTIONS statement. Cynthia        ods _all_ close; ods rtf file='c:\temp\two_images.rtf'; proc sgplot data=sashelp.class; title '1) SGPLOT';   vbar age / response=height stat=mean group=age; run;   proc gchart data=sashelp.class; title '2) GCHART';   vbar age / discrete sumvar=height type=mean  patternid=midpoint ; run; quit; ods rtf close; ... View more