Hi, I found your answer helpful for some scenarios. Thank you!   Now I got a new requirement saying 0 and missing(.) have different meaning. I mean 0 means active item and missing(.) means dead item. So, the output excel file from tagsets.excelxp need to have zero's as zero's and missing(.) in sas table to be blank cell(not empty(which is the result of using options missing=' ', as it a string in output file)) in excel file generated thru tagsets. Please help me if there is a way in doing it.   Chandra ... View more

Hi, Yesterday i was wondering too what was exactly the problem as there is no guaranty of functionning in every cases About wraptext it is by defaut 'yes' in version 1.116 with those remarks about both Andre [pre] WrapText: Default Value 'yes' Values: yes, no, on, off. This value turns wraptext on and off for all style definitions. This option should be used carefully. Wraptext is an attribute which is part of the style definition, specifically, the alignment part. Turning this off will cause all style definitions that are generated afterward, to leave out the wraptext setting. Turning it on and off can work provided you understand that only styles generated from an over ride will be affected by later changes to the setting. This option also interacts with the tagattr wrap setting. If wrap is the opposite of the setting given by this option then it is treated as a style over ride, and a new style is generated with a new alignment tag, which also contain a redefinition of the vertical and horizontal justifications. This interaction means that if you use these options together, it is best to set WrapText at the very beginning and leave it alone. Otherwise the interaction of the options and the styles already created could get complicated. Autofit_height: Default Value 'no' Values: yes, no, on, off. If yes no row heights will be specified. This allows the auto fit height of Excel to do it's job, sometimes not so well. [/pre] ... View more

Hi: Are you using any of the suboptions that normally impact the title??? Also, it depends on whether you mean the SAS title, which comes from a TITLE statement or an Excel header for printing, which comes from the PRINT_HEADER suboption. You will have to look at the output in Print Preview mode to see the impact of the PRINT_HEADER suboption. the &L is the instruction for left-justifying the print header and the &R is the instruction for right-justifying the print header. You can read more about these and other options in the SAS log. cynthia [pre] ods tagsets.excelxp file='c:\temp\just_title.xls' style=sasweb options(doc='Help' embedded_titles='yes' print_header='&L String Left &R String Right' ); title 'SAS Title Centered on Table'; proc report data=sashelp.class(obs=3) nowd; run; title 'SAS Title Centered on Table'; proc report data=sashelp.class(obs=3) nowd; run; ods _all_ close; [/pre] ... View more

Hi: Web Report Studio will NOT use your custom style -- unless you are deploying the style as a CSS definition in the XML that runs on the web tier. Web Report Studio only has 4 styles that it uses by default: FESTIVAL, MEADOW, PLATEAU and SEASIDE. When you run a stored process in Web Report Studio, your output is generated as SASReport XML -- borders and gridlines on the WRS screen are controlled by the interaction between the SASReport XML and the CSS version of the styles that are defined specifically for WRS. When you do an "Export to Excel" from within WRS, the export happens using WRS and Java technology. There is a huge difference between running TAGSETS.EXCELXP code in local SAS or in EG and running a stored process in Web Report Studio. My recommendation is that you work with Tech Support on this question. cynthia ... View more

Found it...!!!! define trans_amount / display "Transaction Amount" format=12.2 style(column)={tagattr="format:##0.00" outputwidth=1in }; or call define(_col_,'style','style={tagattr="formula:R[-1]C+RC[-2] format:##0.00"}'); ... View more

Do you try to use proc formate ? Ksharp ... View more

Hi Cynthia. Million Thanks. You are just great. ... View more

Thanks Chang. I’m somewhat relieved to hear that it looks like a bug to you to. I thought that I was probably overlooking something really obvious. On another side note, how do you add all the colors to the code in your forum postings? ... View more

Hi, It is not clear what kind of output you want?? A report?? A dataset?? What kind of data is this? You say the dataset has the following variables or columns: CODE AMOUNT SINGLE_RECORD_FLAG Then you say you want to set the value of SINGLE_RECORD_FLAG -- what is the current value of that variable? How did it get into the dataset in the first place?? If all you want to do is create or change a variable value that sounds like a job for FIRST.byvar, or LAST.byvar processing or if you want a report for PROC FREQ or PROC MEANS. What have you tried?? Cynthia ... View more

Thanks Cynthia. That's fantastic. ... View more

Hi: Since Information Maps use the Workspace server and since Stored Processes that use Information Maps also need to use the Workspace server and since the Workspace server, in some configurations, uses this information to authenticate/authorize the user, then the use of the ID and password may be required. It does depend on the configuration of your Workspace server. The best place to get these questions answered is to contact Tech Support, because they can help you figure out exactly what is happening and whether the default is required, and whether there's a workaround for the issue -- given your particular configuration environment. cynthia ... View more

Hi Cynthia This is great, but for some reason, I get the error message: ERROR: Insufficient authorization to access c:\your workbook.xls, although it works if I put the file on our server and change the file name accordingly... ... View more

Hi: This Tech Support Note explains the VALIDVARNAME option: http://support.sas.com/kb/14/661.html You may also be interested in this note about setting the VALIDVARNAME option for use with servers in the BI Platform: http://support.sas.com/kb/18/750.html VALIDVARNAME=ANY is usually set automatically by EG because it uses variable names that may have embedded spaces or special characters. The warning doesn't mean you've done anything wrong. It's just means that you have to look at your data and look at the generated code and decide whether VALIDVARNAME is set correctly for your particular situation. If you need help deciding on the correct setting for the VALIDVARNAME option, then your best bet for help is to contact SAS Technical Support. cynthia FYI, the possible values for the VALIDVARNAME= option are -- V7 (default) Allows mixed case, 32 character variable names. Valid characters you can use are alpha, numeric and underscores. -- UPCASE Allows 32 character variable names, but uppercases the variable names. Valid characters you can use are alpha, numeric and underscores. -- V6 Version 6 rules apply. -- ANY Allows variable names to contain special characters. You can use a maximum of 32 characters, stored in mixed case. ... View more

SAS Management console is outside the scope of this group. If searching on support.sas.com and reading the documentation on SMC does not give you the answer you need, then you need to raise this with Technical Support. Kind regards David ... View more

Edited by jp 2/08/09. Message was edited by: jplarios ... View more