About KevinC_

AllanBowe · ‎04-20-2022

I appreciate this post is 12 years old, but my team finally added this feature to Data Controller today! Just upload the excel, enter the password, approve the change, and your password-protected excel data is now in your target SAS table ready to process. Works on ALL versions of SAS (Viya, EBI, Base) and is free for up to 5 users. https://www.youtube.com/watch?v=b2lfBCkdvBI

portiaconant · ‎10-21-2017

I had a similar question. However, this is how I changed the date format within the proc report code instead of in a separate data step. You can create an alias variable for your date variable in the column statement ("date"), and then use the compute function to datepart within the proc report program. Proc Report data = infile; column cut_id sale_date date; define cut_id /format = $10.; define sale_date/display noprint; define date/computed format = mmddyyd10.; compute date; date = datepart(sale_date); endcomp; run;

s_lassen · ‎06-04-2017

@KevinC_: I think the problem is with the IN clause. First, you must make sure that the remote system recognizes IN - you should either use rsubmit; options minoperator; %macro bbb(i); or rsubmit; %macro bbb(i)/minoperator; The first method makes In valid in all macros in the remote session, the second method makes if valid for that specific macro, only. Second, make sure that your WORD_LIST macro variable is not empty, I think that could create a message like the one you got: rsubmit; options minoperator; %macro bbb(i); %if %length(&word_list) %then %if wrd&i in(&word_list) %then %do; If that does not work, check up on the documentation for the MINOPERATOR option.

GenDemo · ‎04-04-2017

Hi All This is great information BTW! I am now also playing around with this, to get dashboards automated. Is there a way to get SAS to push the command to refresh all data (like by clicking the refresh all button on the data tab in Excel), which will refresh all tables, pivots and external data from DBMS connections, without having a maco in the workbook? So I have a xlsx file, not an xlsm file - no macros in the file itself. Thnx GD

Gregor · ‎01-27-2017

Unfortunately, this does not work in my case. I use a similar code but within a loop, where I create an excel file in every step: %let copycmd1 = COPY "&manpath.\Stoch_Vorlage.xls" "&manpath.\Stoch_&klasse..xls" ; 　 data _null_; option noxwait; X &copycmd1; run; libname excel1 excel "&manpath.\Stoch_&klasse..xls"; PROC Datasets lib = excel1 nolist; delete KLASSE; Quit; 　 Data excel1.KLASSE; set ref_&jj; run; 　　　 libname excel1 clear; 　 PROC Delete data = work.ref_&jj; %end; Log tells me my prepared data sheet 'KLASSE' would not exsist and creates a new one 'KLASSE1' NOTE: Libref EXCEL1 was successfully assigned as follows: Engine: EXCEL Physical Name: Q:\[correct directory]\Stoch_12_42 .xls MPRINT(ALLKLASSE): PROC Datasets lib = excel1 nolist; MPRINT(ALLKLASSE): delete KLASSE; MPRINT(ALLKLASSE): Quit; NOTE: The file EXCEL1.KLASSE (memtype=DATA) was not found, but appears on a DELETE statement. NOTE: PROCEDURE DATASETS used (Total process time): real time 0.01 seconds cpu time 0.00 seconds Result: in Stoch_12_42 .xls, KLASSE is not replaced, but the data has been added in a new sheet KLASSE1. There are references from graphics to KLASSE which I do not want to calculate individually but to be created in each loop step respectively. Thanks Gregor

KevinC_ · ‎02-04-2016

Thank you everyone for your input again! I used user24feb's suggestion and it worked for me. Thank you user24feb! :)

ChrisHemedinger · ‎04-02-2015

As Andreas pointed out, FILENAME ZIP can be used to extract the file, and then you can read the result with PROC IMPORT. See examples of using FILENAME ZIP in this blog post. Chris

HENRYROLON · ‎06-19-2015

Thanks, I`ll try this and let you know. Thanks again!

KevinC_ · ‎02-18-2015

Thank you Tom, ballardw, and SASKiwi. Tom, I restarted a new SAS session and now I was able to see more info in the log. The problem was one of the letters in the file name had an incorrect case. It works like a charm now. Thank you everyone!

Kurt_Bremser · ‎01-14-2015

To check, add a statement to the macros in program B like %put 'Macro executed now'; Then look in the log for this message. It may well be that the same macros or any statements that have the same effect are already executed in/from the autoexec.sas Also consider using options mlogic to see when a macro is being executed and what it does.

KevinC_ · ‎11-28-2014

If we can enlarge the box around the legend to make the entire legend look larger would be great too. Thanks!

KevinC_ · ‎07-23-2014

Thank you stat@sas! That worked beautifully.

data_null__ · ‎06-16-2014

The macro language is not well suited to the task of table look up. Consider this approach which does not involve macro language. data base; *example base data to recieve the word holiday; set sashelp.class; run; Data holiday_file(index=(holidays)); input holidays date9.; datalines; 16jun2014 04jul2014 01sep2014 ; run; data base; if 0 then modify base; holidays=today(); set holiday_file key=holidays; if _iorc_ ne 0 then stop; Name='Holiday'; output; stop; run; Proc print data=base; run;

ballardw · ‎03-04-2014

With HTML output I would increase the size of the display area. The 600x400 is pretty small for most of today's monitors and that is part of what is choking your size. Imagefmt=PNG also may give better appearance. The options columns= and Rows= on the Panelby statement is the basic control for appearance. If your data groups exceed the values for row and column then I usually get a new page. Generally if I need to really control the number and content of each display I use data set option where clauses to restrict each created panel to a desired set of values and make multiple calls to procedure. With your 9 panels example I would start with columns=3 and rows=3 ...

Lenvdb · ‎08-06-2014

Did you ever get a solution with this issue? I am now having a similar issue and found by inserting this line I can do it: USE <databasename>; PROC SQL; connect to odbc as sasx(dsn="SERV1"); Execute(USE &db; /*==specify your database===*/ Insert into cust_table1 (cust_id, loan_count, category) select cust_id, loan_count, category from cust_data )by sasx; disconnect from sasx; QUIT;

Online Status	Offline
Date Last Visited	‎06-01-2017 04:12 PM

Macro Error Question

Re: Passing a comma delimited variable to a Macro

Re: Passing a comma delimited variable to a Macro

Passing a comma delimited variable to a Macro

Re: Proc Report Date Format

Proc Report Date Format

Read a zipped Excel file ??

MAP data at the CBSA level ??

Re: X command in PC SAS

Re: X command in PC SAS

Import a password protected Excel doc

Re: Import a password protected Excel doc

Re: Import a password protected Excel doc

Re: Proc Report Date Format

Re: Macro Error Question

Re: Refresh Excel Pivot from SAS ??

Re: Proc Export Replacing Excel Sheet ??

Re: Passing a comma delimited variable to a Macro

Re: Read a zipped Excel file ??

Re: MAP data at the CBSA level ??

Re: X command in PC SAS

Re: Can you trigger a macro by using a %include ??

Re: EG 5.1 Map Legend Size

Re: How to include a leading blank in a macro variable ?

Re: SAS Macro Question

Re: Proc SGPANEL Question ??

Re: Pass Through SQL to Append/Update a SQL Server Table?