Thank you for your reply, I hope this information explains it better.   Which ODS destination do you want to use?  _ODSDEST=TAGSETS.EXCELXP   SAS Version:  9.2   And what type of "vertical" do you want? Reads top to bottom, bottom to top, letters with normal orientation or rotated (on their side or upside down) Is this only for column headers or elsewhere in the table?   I want the column headers and column values vertical, example: ColumnHeader     ColumnValue AccountNbr             3301 RecvdToDate          10050.00 PeriodYear              2014 OtherData                xyz   AccountNbr             3302 RecvdToDate          567810.00 PeriodYear              2015 OtherData                abc   Note: This is a small representation of the columns. The data for each ‘AccountNbr’ will be summarized by year and the user wants the output to be printed (as excel) in the above format. For each AccountNbr, the columns will be repeated and will be printed (vertically). ... View more

Meant to add INPUT: newvar = input(put(oldvar, IS8601DN10.), yymmdd10.); ... View more

Your data is on the server, not on your C drive. You can export it to the server and then FTP it off. Are you using Base SAS? If so you may be able to use the following to get it to your local drive: libname rmtwork slibref=work server=YOURSERVER; Then do a proc export with: RMTWORK instead of WORK. ... View more

Ok... I'll give it a try!  Thanks. I'll let you know how it goes, may be tomorrow before I get back to it. ... View more

Hi:   Here are some examples of using PROC TABULATE to get both counts and statistics. Each TABLE statement produces 1 table. The 4th table uses a numeric variable in order to request MEAN statistic for MPG_CITY and MPG_HIGHWAY for each MAKE and TYPE, just to show a cross-tabulate. SASHELP.CARS has a LOT of car brands in the file, so I limited the MAKE variable to only 5 values to loosely correspond to your description. cynthia ods listing close;   title; footnote; ods html file='c:\temp\car_info.html';   proc tabulate data=sashelp.cars;   where make in ('Acura', 'Audi', 'Toyota', 'Volkswagen', 'Saturn');   class make type ;   var mpg_city mpg_highway msrp;   table make all,         n / box='1 Make in Rows';     table make='2 Make as Columns' all ;     table type all,         make*n all*n/ box='3 Cross-Tab';      table type all,         make*(n='Count' mpg_city*mean mpg_highway*mean) / box='4 Average MPG';   run; ods html close; ... View more

Hi:   Usually, in this situation, you have your batch job write the .xml files to a directory. Then, you have a VBScript that reads the directory, opens each file as XML and resaves it as an XLS or XLSX file. Once the file is resaved, you can "empty" the original directory, by sending the original output to archive or changing the file names or even deleting the original files. Then the directory is ready to receive the next night's output from the batch job.   The only way to make proprietary Excel files is through the use of PROC EXPORT or the LIBNAME engine. If you use ODS, you are creating an ASCII text file (CSV, HTML or XML) that Excel knows how to open and render.   The far easiest way to deal with this is to educate your users that it is perfectly acceptable in Excel to open an .XML file using FILE--> Open. On the Excel Open menu, they only have to look for a file type/extension of .XML Files  XMLIf they really want to see the .XLS extension, then teach them how to do the File --> Save AS. You can even show them that .XML is an acceptable file type to open (see screenshot). cynthia ... View more

Hi, Not sure if there is an easy answer.  I would suggest just entering the prompts yourself, rather than having SAS search your code to guess at what might be prompts (which is what I think of from the 'prompt from SAS code' button).  It's not surprising to me that global macro variables that are commented out might still be seen by the 'prompt generator' routine, because it might not know enough about the SAS language to recognize all the different kinds of comments.  I think it's easier just to make a list for yourself (perhaps in a header comment block), defining all the prompts your code expects, and then use that list to create the prompts. HTH, --Q. ... View more

ncsthbell, I say only that you do not need 3 database connections (usernames/passwords) if you have everything  in one database. After the execution of this SQL-script, you can manage in your SAS-program the Oracle connections (only) with your access. Regards, Sándor ... View more

Thanks RickM!! ... View more

Hi, You don't have to create your own code, EG creates the code automaticlly when you use query builder(you can look at the code  by clicking "code" tab) ,you only need to modify the code. Please check the attached screenshot. Hope this helps.  - Linlin ... View more

You could save the prompt values to a temporary table and then recover them when needed in the linked reports.  This link shows how to do a single set of prompts for a multi-section report.  Linked reports would use a similar pattern.  You just need to place a stored process in the linked report to recover the saved prompt selections. http://support.sas.com/kb/40/758.html ... View more

Thanks, I'll try that. ... View more