Hi:
As I said, without seeing the indenting (or seeing some code) it is impossible for me to imagine what you want or are describing for the Consortia column.
For example, where does the number "59" go??? In the # in Grant column?? Where does the number 5 go? In the same column?? Is "PI:" something that goes in the Consortia column??? or is the whole string "PI: Knowles" something that goes in the Consortia column???
What about MCC??? Is that a Consortia? Why doesn't it have a : and a name after it??? Also, most of the lines have ## 590x on them -- for example:
[pre]
59 5903
5 5901
[/pre]
But what about the Pilger line??? there's no number before 5902 -- so should this 5902 line up underneath the 5903 and the 5902 or underneath the 59 and the 5.
This is why I referred you to the forum topic on posting code -- not just so you could indent the report so we could see what you want to do with the Consortia column, but also since you are posting code that has < and > symbols -- sometimes if you have too many of those brackets in your code, the HTML that governs the postings gets confused and so you have to replace all < symbols with < and all > symbols with > for posting purposes. Not a big deal and you can do it with a global search and replace in NOTEPAD just before you post output or code to the forum.
As it explains in this posting:
http://support.sas.com/forums/thread.jspa?messageID=27609毙
Surround code snippets with [pre] and [/pre]
This changes to a typewriter font and retains spaces and
line breaks. So
[pre]
proc print data=sashelp.class;
var name age height;
run;
[/pre]
becomes
[pre]
proc print data=sashelp.class;
var name age height;
run;
[/pre]
(Note how the 2 spaces before the VAR statement are respected in the "pre-formatted" or typewriter font. And I did actually type 2 spaces before the VAR statement in the posting editor window....but the 2 spaces only show in the typewriter font view of the posting.)
If you are unable to post a view of the output with indenting that illustrates how the Consortia column appears now ... so we can visualize the difference between what you have and what you want, then providing code that produces a similar report -- perhaps using SASHELP.SHOES would give folks a concrete way to run REPORT and see what's happening and then figure out how to change the REPORT code to do what you want.
cynthia