Ok may be because the format of the "format" column (:-)) is 49 chracters wide and if you adjust for it as below it selects   PROC SQL; SELECT * FROM sashelp.vcolumn WHERE TRIM(format) = 'DATE9.'; QUIT; Did it work? Please let me know. ... View more

That is a little strange because when I did the following it worked ..   PROC SQL; SELECT * FROM sashelp.vcolumn WHERE format LIKE 'DATE9.'; RUN; ... View more

@Kurt_Bremser Thank you. ... View more

Will PROC SQL be a bad idea? Just curious .... also you did not mention how big is the data you have. This is the question I have (to others seeing this message as well) .. is it better to use MERGE in DATA step or use PROC SQL? Under what conditions we should sway towards one method rather than the other? SAS experts here please. ... View more

Elegant ... View more

Hi. There was an issue with the data as there was forward slashes between patientid and date2. I removed them and replaced Y with numbers to show that it is working.   Here is the code, if you want to try. Please let me know if this is what you wanted. I might have read the requirements wrong. After the code is the output     data b; input patientid date2 : mmddyy10. x1 x2 x3 x4 x5 x6 x7; format date2 mmddyy10.; datalines; 4 5/5/2009 1 . . . . . . 4 5/5/2009 . 2 . . . . . . 4 5/5/2009 . . 3 . . . . 4 5/6/2009 4 . . . . . . 4 5/6/2009 . 5 . . . . . . 4 5/6/2009 . . 6 . . . . 4 5/6/2009 . . . 7 . . . 4 5/6/2009 . . . . 8 . . 4 5/6/2009 . . . . . 9 . 5 5/5/2009 1 . . . . . . 5 5/5/2009 . 2 . . . . . . 5/5/5/2009 . . 3 . . . .; run; PROC REPORT data=b; COLUMNS patientid date2 (x1 x2 x3 x4 x5 x6 x7); DEFINE patientid / GROUP; DEFINE date2 / GROUP; DEFINE x1 / ACROSS SUM; DEFINE x2 / ACROSS SUM; DEFINE x3 / ACROSS SUM; DEFINE x4 / ACROSS SUM; DEFINE x5 / ACROSS SUM; DEFINE x6 / ACROSS SUM; DEFINE x7 / ACROSS SUM; RUN;     Output ... View more

@jennifert .. Does it also take into account "total" width of all columns? Are there two checks? One for number of columns and one for total width. Which ever one fails first, it stops displaying onwards. I am asking this because looking at the height of the scroll bar for columns ..may be there are not 30 columns .. Regardless, I thought I will ask this.  ... View more

@jennifert Thank you from my side .. even though I am not the one who asked. ... View more

I see your problem. I had a hunch that I was underestimating your problem and I did. I don't have the perfect answer but there is a two step workaround.   In the Columns box (which you highlighted as a red box) ..if you go up it says "Seleziona tutto" .. I guess that means "select all". If you click, it will select all columns and solve the problem. However you are right, you will have to do it for every dataset that you open.   I guess it happens from 33 columns onwards. May be it displays 32 columns only and rest you have to select.  May be this is a default setting in SAS and there may be a way how we can override this.   SAS experts may please comment on this. ... View more

I think if you scroll to the right, you should be able to see all the columns. Since screen width is fixed and limited, only so many columns can be seen at a time. By default Studio outputs 100 rows (you can see rest of rows by clicking arrow at the top) and a few columns. ... View more

Will it matter if you achieve the same result with PROC REPORT instead of PROC TABULATE? ... View more