It is hard to assume anything based on the volume of data you have provided. Are the fields supposed to be fixed width?  If not, how do you know where each field ends? The following should be pretty self explanatory. data want; infile datalines; INPUT @1 var1 $2.       var2 6.       var3 $8. ; datalines; BE123456AAA NL987654BBBBBBB ; run; ... View more

The CLASS statement in Proc Summary (or Means) will only return one value per group.  To get what you want you can use sql. proc sql; select sex, age, name from sashelp.class group by sex having age=max(age); quit; ... View more

Hi. First thing: you should never give a real path on your machine. Second, when I ran your code (replicated below) it worked. So please provide some log file, or something more. ods listing close; *define the path once, no need for quotations, just simply \\my_path_where_I_keep_things\... %let path = your_path; ods html file = "my_graph.htm"     path = "&path." (url = none)     gpath = "&path." (url = none); filename my_graph "&path.\my_graph.png"; goptions reset = global gunit = pct border cback = white htext = 2 ftext = "Arial"     device = png gsfmode = replace gsfname = my_graph     rotate = landscape autosize = on xpixels = 1100 ypixels = 800 ;     proc gchart data = sashelp.class;         vbar age/group = sex name = "my_graph";     run;quit; Good luck! ... View more

Hi:   I notice that you open ODS HTML, but you close ODS HTML3? I assume that is a typo.   I'm not sure what popup box you mean -- is this one of the Windows popups? I used to see one all the time with RTF or PDF output -- http://support.sas.com/kb/9/627.html http://support.sas.com/kb/13/128.html   Sometimes you can stop that from happening by going to Tools-->Options-->Preferences-->Results and turning OFF the "view results as they are generated" choice. But I haven't seen those type of messages in a while. But, as I said, I never saw this popup with ODS HTML output, so this is unusual.   Or, if you have Excel 2007 or 2010, you might be seeing popup messages that says "The file that you are trying to open "file" is in a different format than   specified by the file extension. Verify that the file is not corrupted and is from a  trusted source before opening the file. Do you want to open the file now?"   This Tech Support note describes the note with ODS MSOFFICE2K and ODS TAGSETS.EXCELXP but you could also get it with ODS HTML or ODS HTML3: http://support.sas.com/kb/31/956.html   The reason for this second message is that when you use ODS HTML, ODS HTML3 or ODS MSOFFICE2K you are NOT creating a true, binary .XLS file in the proprietary Excel structure. You are merely creating an HTML file that Excel knows how to open and render. You are fooling the Windows registry into launching Excel when you double click because the registry has the .xls file extension associated with Excel. The true file extension for your file, when created with ODS should be .HTML or .HTM -- but then Windows would launch a browser.   ODS is creating an HTML file for you. You name it .XLS to launch Excel. That does not change the underlying fact that if you open the file with Notepad you will see HTML tags.   So, depending on what message you're seeing the fix might be one of two different things. If you're not seeing either of the above popup messages, then it might be good to work with Tech Support. If it is a popup that is new or a new situation, they can modify an existing note or issue a new note to help other folks. cynthia ... View more

Hi --   Changing from 9.2 to 9.3 would be a difference, but the change would be from the gray and blue default colors of 9.2 and STYLES.DEFAULT to the new white and light blue colors of STYLES.HTMLBLUE instead of SEASIDEPRINTER style. So, in 9.2, if SEASIDEPRINTER suddenly was not available, then STYLES.DEFAULT would be used; in 9.3, if SEASIDEPRINTER was not available, then STYLES.HTMLBLUE would be used.   But I just noticed this statement in the OP (highlighting mine): ods html file="\\....\HU.xls" rs=none style=seasideprinter; The file extension is .xls -- which is a trick to fool the Windows registry into launching Excel. Microsoft is pretty good about opening HTML files (which is what ODS HTML is really creating). I wonder whether some setting changed. When version 8.2 was active, the "flavor" of HTML created was HTML 3.2 -- and all the style information was embedded in the HTML tags. Microsoft liked HTML 3.2. When SAS version 9.x came out, the default "flavor" of HTML created was HTML 4.0 -- and all the style information was embedded in an inline <STYLE> section that Microsoft didn't like. Microsoft didn't like HTML 4.0 so much, that for Office 2000, they designed their own "flavor" of HTML tags, and their own version of an inline style. There was a registry switch that you could set that told SAS whether to create HTML 3.2 or HTML 4.0 when the simple ODS HTML statement was used. SAS/IntrNet folks used to do that switch with the registry a lot because most web servers at the time were happier with HTML 3.2 and nobody wanted to change their programs.   So, another thing that the OP could try would be: ods html3 file="\\....\HU.xls" rs=none style=seasideprinter;   and see whether Excel is happier with the file when this destination is explicitly used (ODS HTML3 explicitly creates HTML 3.2 tags). If that works (and seasideprinter is used inside Excel when the HTML file is rendered), then that says the item store is still OK. In fact, I forgot to suggest that you could just look inside the HTML file with Notepad and look for the inline style section. If some of the colors and fonts look the same as those in SEASIDEPRINTER style, then that's another clue that the item store is OK. Also, I thought about it and the problem could be with Excel -- perhaps there was a recent upgrade to Excel that caused the HTML inline style section to be ignored. If you use either of these invocations, Excel generally "likes" the type of style information created by either of these destinations (because both produce Microsoft "flavor" of HTML): ods msoffice2k file="\\....\HU.xls" rs=none style=seasideprinter; ods tagsets.msoffice2k_x file="\\....\HU.xls" rs=none style=seasideprinter; Excel likes the type of style section created by msoffice2k and msoffice2k_x -- so these might open better, especially with Excel 2007 or 2010. cynthia ... View more

Hi:   If you are only using the SKIP variable for your forced page break, try this combination of BREAK/RBREAK statements: BREAK AFTER gr_age    /  SUMMARIZE    ; break before skip / page ; RBREAK AFTER  /  SUMMARIZE  ; I believe that you will get the grand total placed on the last page if you do a BREAK BEFORE SKIP. Also, I would recommend that you make the GR_AGE variable an ORDER variable instead of a GROUP usage variable. You should be seeing this in the log: NOTE: Groups are not created because the usage of xxxxxx is DISPLAY. To avoid this note, change all GROUP variables to ORDER variables. cynthia ... View more

I Google it. Found it. http://www.caspur.it/risorse/softappl/doc/sas_docs/mddb/z1019824.htm Ksharp ... View more

Yes, LINE statements are always executed even when they're within the scope of an IF or DO. LINE statement behavior is counter-intutitive (to say the least). When PROC REPORT executes a COMPUTE block, it first removes all the LINE statements, then executes the remaining code, and only then executes the LINE statements in the order they appear in the COMPUTE block. See the Restriction here. However, this SAS note describes a clever trick that allows a LINE statement to appear to be conditionally executed. ... View more