About SASMike

SASMike · ‎04-25-2016

Thanks Quentin. :) I agree. I'll have to create a work-a-round with a macro.

SASMike · ‎04-25-2016

Is it possible to resolve a macro variable within a PROC SQL view at execution time? I have a query with a dynamic FROM reference and I'd like to create a view without the current value of that macro being stored with the definition of the view. I've tried SYMGET() to no avail. Here's my example. I'd like to be able to change MYMACROVARIABLE from table1 to table2 without having to redefine the view. PROC SQL; CREATE VIEW test AS SELECT * FROM &MYMACROVARIABLE; QUIT; Any feedback would be appreciated! :) Thanks!

SASMike · ‎01-13-2016

Here's an example of the Fibonacci using an array. *OUTPUT THE FIBONACCI SEQUENCE TO THE SAS LOG; DATA _NULL_; ARRAY FIBONACCI {100}; DO I=1 TO DIM(FIBONACCI); IF I<=2 THEN FIBONACCI{I}=1; ELSE FIBONACCI{I}=FIBONACCI{I-1}+FIBONACCI{I-2}; PUT FIBONACCI{I}; END; RUN;

SASMike · ‎03-06-2015

Here's a reference article I found handy for working with the in operator in macros. It entails listing the 'in' delimiter. Hope this helps! Sample 35591: How to use the new macro IN operator for SAS 9.2 http://support.sas.com/kb/35/591.html Starting SAS 9.2, there is an IN operator for the macro language. The IN operator can now be used on the %IF statement when the MINOPERATOR option is set on the %MACRO statement or as a SAS system option. options minoperator mlogic; %macro test(value)/mindelimiter=','; %if &value in 1,2,3,4,5,6 %then %put Value found within list.; %else %put Value not in list.; %mend;

SASMike · ‎03-05-2015

If you're using Enterprise Guide and receiving this message, you can adjust the maximum number of rows to display. The option is under Tools - Options - Performance - Maximum number of rows to display...

SASMike · ‎10-21-2014

It depends. Just like a carpenter may use different tools for different tasks, a SAS programmer will either use the DATA step or PROC SQL step depending on the circumstances. The DATA step is very useful when you need to implement business logic or do heavy manipulations on your data. Meanwhile, PROC SQL is useful for mining from a variety of datasouces. Once you become familar and comfortable with both steps, you'll develop a propensity to use the most applicable step depending on the situation. In a nutshell, DATA step is great for business logic and heavy data manipulations. PROC SQL is great and intuitive for mining and combing many data sources. I'd check out this paper for an introduction to the differences between the DATA step and PROC SQL: http://www2.sas.com/proceedings/sugi29/269-29.pdf. Happy Programming! :smileysilly: SAS Mike

SASMike · ‎01-15-2014

Solution Follow-Up: I was able to find a solution to this problem by installing the newest version of the ExcelXP tagset from this link: Base SAS: ODS MARKUP There is a help note about installation here: 32394 - Installing and Storing Updated Tagsets for ODS MARKUP This solved the issues I was having with the 'minimal' style. I cannot guarantee this will solve the issue for everyone, however, it did work for me. Thanks all!

SASMike · ‎01-15-2014

That explains a lot. I will have to incorporate another style to circumvent this issue. Thank you very much !!!

SASMike · ‎01-14-2014

I'm not sure why :smileyconfused: but when using the 'minimal' style, there are issues when using a COMPUTE block. The errors that are generated relate directly to those COMPUTE lines. Unless someone has a solution, I'll have to build a workaround. Appreciate your response ! COMPUTE AFTER /* STYLE=[] */; LINE ""; LINE "1. Footnote one"; LINE "2. Footnote two"; LINE "https://www.google.com"; ENDCOMP; The four COMPUTE lines each generate an error in the Excel log file.

SASMike · ‎01-14-2014

Greetings! I have been acclimating myself to the ODS ExcelXP facility lately and I've run into an issue generating files. The issue only occurs when using the "minimal" style oddly. The SAS log does not generate any errors but when attempting to open the spreadsheet (via Excel 2010) I run into the following error. Other styles work perfectly and do not generate errors - just minimal. I've verified that the "minimal" style works perfectly with other outputs (HTML, PDF). I've even opened the style CSS itself and confirmed it's existence. It does not matter if I use the extention .xls or .xml...same error. Any help would be much appreciated! Thank you!!! SAS Mike Excel error upon attempt to open: Here's the Excel log file: XML ERROR in Table REASON: Bad Value FILE: C:\Users\kj1062\Desktop\myexcel.xls GROUP: Row TAG: Cell ATTRIB: StyleID VALUE: notecontent__c XML ERROR in Table REASON: Bad Value FILE: C:\Users\kj1062\Desktop\myexcel.xls GROUP: Row TAG: Cell ATTRIB: StyleID VALUE: notecontent__c XML ERROR in Table REASON: Bad Value FILE: C:\Users\kj1062\Desktop\myexcel.xls GROUP: Row TAG: Cell ATTRIB: StyleID VALUE: notecontent__c XML ERROR in Table REASON: Bad Value FILE: C:\Users\kj1062\Desktop\myexcel.xls GROUP: Row TAG: Cell ATTRIB: StyleID VALUE: notecontent__c Here's my SAS code: ODS TAGSETS.ExcelXP FILE="C:\Users\kj1062\Desktop\myexcel.xls" STYLE=minimal OPTIONS ( EMBEDDED_TITLES='Yes' SHEET_NAME='PROC PRINT' FROZEN_HEADERS='3'); TITLE BOLD COLOR=BLACK "ODS Excel Test - PROC PRINT"; PROC PRINT DATA=SASHELP.CARS OBS='Observation #' SPLIT='*'; *SPLIT implies LABEL; VAR Make / STYLE=[JUST=RIGHT TAGATTR='format:text']; VAR MSRP; WHERE Make='Audi'; RUN; ODS TAGSETS.ExcelXP OPTIONS ( SHEET_NAME='PROC REPORT'); TITLE BOLD COLOR=RED "ODS Excel Test - PROC REPORT"; PROC REPORT DATA=SASHELP.CARS (WHERE=(Make='Porsche')) MISSING NOWD STYLE(HEADER)=[FONT_WEIGHT=BOLD JUST=CENTER BORDERWIDTH=1] STYLE(COLUMN)=[JUST=CENTER BORDERWIDTH=1]; COLUMN Make MSRP; DEFINE MSRP / F=DOLLAR20.; COMPUTE AFTER /* STYLE=[] */; LINE ""; LINE "1. Footnote one"; LINE "2. Footnote two"; LINE "https://www.google.com"; ENDCOMP; RUN; ODS TAGSETS.ExcelXP CLOSE;

Re: Resolve Macro Variable At Execution within PROC SQL VIEW

Resolve Macro Variable At Execution within PROC SQL VIEW

Re: how to display a fibonacci series using base sas concepts

Re: 'in' operator after %if in macro

Re: Warning Message

Re: data steps versus proc sql

Re: Help with ODS ExcelXP errors using STYLE=minimal

Re: Help with ODS ExcelXP errors using STYLE=minimal

Re: Help with ODS ExcelXP errors using STYLE=minimal

Help with ODS ExcelXP errors using STYLE=minimal