Not too sure I understand your question. This aside, it may be better to use this in your case: proc datasets noprint mt=data; save TABLE1TOSAVE; run; rather than the kill option, to avoid copying data back and forth.     ... View more

You have two options here that I see.    1. Import the Excel file as is and develop (manual) program that will check each variable type and if not then it converts it to the type and format desired.  2. Convert the Excel files to CSV - using a VBS script, see link below, and then use a standard data import to import all at once. You could also automate this entire procedure if so inclined, to download the file, convert and then import.  http://support.sas.com/kb/43/496.html   Personally, I'd go with Option 2 because I'm lazy...but you can do Option 1. It'll likely end up being a macro and you can use VTYPE to check a variables type. If you do decide to go with Option 1, I would recommend first creating a file with the master variable list and types and use that to drive your program so it's still automated in a fashion.  ... View more

Well...the error is correct, SQL doesn't have the concept of row order, it operates on the entire data set.    What are you trying to do here? I suspect BY group processing within a data set is more efficient. ... View more

PROC SORT DATA=WORK.QUERY_FOR_APPEND_TABLE_0001(FIRSTOBS=1 KEEP="At Risk?"n Origin Destination Units "% OT"n "% <1"n "% <2"n "% <4"n "% <6"n "% <12"n "% <24"n "<48"n) OUT=WORK.SORTTempTableSorted ; BY "At Risk?"n; RUN; TITLE; TITLE1 "Report Listing"; FOOTNOTE; FOOTNOTE1 "Generated by the SAS System (&_SASSERVERNAME, &SYSSCPL) on %TRIM(%QSYSFUNC(DATE(), NLDATE20.)) at %TRIM(%SYSFUNC(TIME(), TIMEAMPM12.))"; PROC PRINT DATA=WORK.SORTTempTableSorted NOOBS LABEL ROWS=PAGE ; VAR "At Risk?"n Origin Destination Units "% OT"n "% <1"n "% <2"n "% <4"n "% <6"n "% <12"n "% <24"n "<48"n; BY "At Risk?"n; PAGEBY "At Risk?"n; SUM Units "% OT"n "% <1"n "% <2"n "% <4"n "% <6"n "% <12"n "% <24"n "<48"n; LABEL "At Risk?"n=" "; RUN; /* ------------------------------------------------------------------- End of task code ------------------------------------------------------------------- */ RUN; QUIT; %_eg_conditional_dropds(WORK.SORTTempTableSorted); TITLE; FOOTNOTE; ... View more

Hi:   This is something you might want to try with the List Report task instead of Summary Tables task. Or else learn PROC REPORT code. This is easier to do with PROC REPORT than with TABULATE.     As an example -- the top table is PROC TABULATE on a subset of SASHELP.SHOES and the bottom table is the PROC REPORT TABLE showing the region on each row, as you want.     Here's the code: title; footnote; PROC TABULATE DATA=sashelp.shoes; where product in ('Boot' 'Sandal' 'Slipper') and region in ('Asia' 'Canada'); VAR sales; CLASS region product ; TABLE /* Row Dimension */ region*(product ALL={LABEL="Total (ALL)"}), sales* Sum; RUN; proc report data=sashelp.shoes; where product in ('Boot' 'Sandal' 'Slipper') and region in ('Asia' 'Canada'); column region show_region product sales; define region / group noprint; define show_region/ computed 'Region' style(column)=Header; define product / group style(column)=Header; define sales / sum f=dollar14.; break after region / summarize style=Header; compute before region; hold = region; endcomp; compute show_region / character length=30; show_region = hold; endcomp; compute after region; show_region = "Total (ALL)"; endcomp; run;     Hope this helps, cynthia ... View more

If your server is connected you shouldn't...only if you're working locally.  But there may be something about your set up that we don't know, so I'd follow your companies advice for now 🙂 ... View more

Look at the code, is it proc summary or proc tabulate? ... View more

I generally connect with a LIBNAME statement and then use that in PROC SQL.  This way I can use one connection for both implicit and explicit pass-through SQL. For you it would probably look something like this: LIBNAME OracSAS ORACLE USER=&UserNm PASS=&PassWd PATH='EDWP' SCHEMA=IDWE CONNECTION=GLOBAL; PROC SQL; CONNECT USING OracSAS AS OracDB; /* CODE */ DISCONNECT FROM OracDB; QUIT; ... View more

Hi   In the Summary Table wizard page 2, bottom right, this is where you can specify a format like TIME8.   If you need to have different formats depending on the column, you have to use just the Summary Tables. ... View more

You need a licence and install SAS/ACCESS to Oracle or ODBC. If you have that already follow the instruction in the corresponding documentation. ... View more