About KarlK

KarlK · ‎03-09-2012

I'm sure you're right, Ksharp. I saw a couple ambiguities in the original specs that I just chose to ignore. I couldn't decide if "each and every transaction" in criterion #2 meant "starting with the very 1st" or "starting with the 1st that meets criterion #1". And, if the latter, does that that mean that a branch with, say, 19 transactions that fail criterion #1 followed by 1 transaction that meets it, should be output, but a branch with 19 that do followed by 1 that doesn't gets flushed. That didn't make sense to me, so I just used opendate to get the discussion started. I also wondered if the target date of 201104 was a constant or was intended to be a stand-in for max(trandate). And, if the latter, is that by branch or for the table as a whole. So again, I just took the easy way out. If, in fact, there are any transactions after that date, my algorithm fails (as, I think, does yours.) Anyway, if the OP wanted to clarify the specs, this has been a good discussion, I think. And hey, my SQL solution was kind of elegant, no? Wrong, but elegant. Karl

KarlK · ‎03-08-2012

%let yyyy = %sysfunc(year(%sysfunc(inputn(&yymm,yymmn4.)))); HTH, Karl

KarlK · ‎03-08-2012

I think you can get pretty close with a SQL query. But let me make a couple assumptions. First, [both PRODUCTS show both PMTS & EXPNS at each "future QTR"] means: shoes='S' and clothes='S' and pmts>0 and expns>0. Second, [Transaction are occuring at EACH and EVERY subsequent TRANDATE QTR up to 201104] means at least 1 row which meets criterion #1 for each quarter between opendate and 201104. (You said "trandate" but that doesn't make sense to me.") Third, you can convert opendate from a year+qtr to an actual SAS date, because my solution uses the SAS intck() function, which needs dates. You can use the SAS yyq() function for this. My solution gets at criterion #2 by counting the unique rows which meet criterion #1 and comparing that to the total number of actual calendar quarters between opendate and 10/01/2011 (the SAS representation of QTR 4, 2011). If they are equal, then criterion #2 is met. So take a look and see if you think this is what you want. "Have" is your dataset above, except, as I said, opendate has been converted to a SAS date, not what appears to be YYYYQQ text string in your dataset. proc sql; select opendate, branch, intck('QTR',opendate,'01OCT2011'd)+1 as nquarters, count(*) as ntrans from (select distinct opendate,branch,trandate from have where shoes='S' and clothes='C' and pmts>0 and expns>0) group by opendate,branch having nquarters = ntrans ; quit; Karl

KarlK · ‎03-07-2012

I have not tested this, but just looking at your code, it appears you have an extra semicolon. Try it without the semicolon after the "6". In other words: if &day = 6 then do; Karl

KarlK · ‎02-27-2012

Not arguing, Art, just taking a learning opportunity. I get the "query requires remerging" message from your query, so Proc Sql technically is reading the data twice, no? Also, SasPhile, Art's elegant query reproduces the duplicate record you have in your original dataset. If you don't want that, you can add "distinct" as in "select distinct *. . .". Karl

KarlK · ‎02-21-2012

Alphanumeric, Cynthia is, of course, right. What's catching you is her first tech note, I believe. Your post caught my eye because, unlike Robert Allison (who knows 13 million times more about SasGraph as I do), I mix graphics and text on PDFs all the time, and I knew your program "should" work. My workaround has just been to output a placeholder string in place of {lastpage}, not used anywhere else in the document, and then do a global search & replace in Acrobat. Sorry I didn't see your post sooner. Karl

KarlK · ‎02-17-2012

Hmmm, I see what you're saying, Cynthia. I got the same results you did. Perhaps the OP is doing some styling s/he didn't mention that is having some inheritance side effects. Anyway, OS2rules, now that I'm back at my own box, I took Cynthia's code and just stuck a style over-ride on the rbreak statement, rather than going to the trouble of running Proc Template. If you wanted to go with this solution, you'd need to change my "{color=red}" to set the style attributes that are wrong in your case. This is just a quick & dirty example: (. . . Cynthia's code up to the rbreak line . . .) rbreak after / summarize style={color=red}; run; If you wanted to post more of your code, we might be able to diagnose why your rbreak line is screwy. I'm kinda curious about that. Karl

KarlK · ‎02-17-2012

Here's a quick answer which I hope points you in the right direction. I'm sorry I can't test it right now. The style element for RBREAK lines is DataEmphasis. So in your Template modification, you should be able to add a "class DataEmphasis / ..." and style that. I suspect you can also style the RBREAK section directly in the Proc Report, but, again I apologize, I'm not at a SAS machine at the moment to be more helpful. If this doesn't help, post back here and I'll take another crack at it later. Karl

KarlK · ‎02-17-2012

Put double quotes around the string macro in the substr() invocation. (Untested). FILE_PERIOD = SUBSTR("&FILE1",7,10) ; Karl

KarlK · ‎01-26-2012

Sure. 2 dots after the &i: infile "c:\x.&i..txt"; The 1st dot terminates macro replacement, and the second is the literal "." before the extension. I'm glad my earlier response helped. Good luck.

KarlK · ‎01-26-2012

If I understand correctly, you need another leading ampersand in 1559: set &&file&i;

KarlK · ‎04-21-2010

Duh. (Slaps forehead with palm.) I've done that many times with a style element I created in an ODS template. My brain was in HTML/CSS mode and I just didn't generalize. Thanks, Kevin.

KarlK · ‎04-21-2010

I have a data-driven website, not generated in SAS, that displays various data tables on a single web page linked to a single CSS stylesheet. The different tables use different color schemes, depending on their content. This is accomplished using class attributes. So, the base table has, for example, black text in the header, and the corresponding style element is something like "th {color: #000000}". Another table type has red header text, with a style element like "th .header2 {color: #FF0000}. In the html for the table, the latter would appear as "text. I'm now trying to do the same thing in SAS. I've changed all the class names in the stylesheet to be compatible with what SAS expects in ODS cssstyle= in 9.2, and it works for the base table type. What I can't get it to do is give me the alternate styling for the second table type. I tried something like: proc print data=sashelp.class (obs=5) style(header)=[class="Header2"]; run; SAS produced html like: Text I was glad to see the "Header2" in the class element, but SAS followed it with the inline "style=..." which set all the attributes back to the base table header element. I confirmed that the "style=" was the problem by manually editing the html to remove that. Then the file displayed correctly in the browser with the Header2 style. Is it possible to use a customized css stylesheet and use your own class attributes for some of the table elements? I can see a workaround where I use style= in proc print/report to over-ride the defaults, but the straight html way I'm doing now (not using SAS) seems so much more elegant. Thanks in advance, Karl

KarlK · ‎04-07-2010

Maurice, This is a long shot, so if it doesn't work, I won't be surprised and apologize in advance for wasting the bandwidth. Try changing your escapechar, to something like '^'. In my experience, '\' is unreliable as an escapechar. Why? I don't know for sure, but my theory is that: 1) windows tries to use it as a sub-directory separator as in unix and gets confused in the ods context; 2) the RTF specification uses it as it's own escape character and ODS and RTF may be interacting in some way and so it doesn't behave as expected. As I say, it's a long shot. Good luck.

KarlK · ‎03-30-2010

I don't know how to control a box in sas graph, but what about "ods text" with a style? Here's a simple example which I stuck right after the "run;" of the preceding procedure. When I ran it, I got a blue box that was tight up against the text on all 4 sides. (Note, it assumes ods escapechar='^'.) ods html text = "^{style [bordercolor=blue]This is text with a blue box around it}"; This uses SAS 9.2 syntax for the inline style. If you're using an earlier version, you'd need the old ^S={} syntax, but I think the "bordercolor" attribute has been around for a few versions now, so it should still work. Karl

Online Status	Offline
Date Last Visited	‎12-02-2015 11:22 AM

Re: Identifying a sequence of events

Re: ODS HTML: Just the file, please.

Re: Cannot insert today() via PROC SQL ?

Re: Emailing the contents of the program editor window

Re: Emailing the contents of the program editor window

Re: Emailing the contents of the program editor window

Re: Pass-Through automatic variable does not work

Re: Proc Tabulate - Multiple Formats In One Column and Header Rows Wit...

Re: How to handle DBCS Character in datasets ?

Re: Change a Dates Format

Re: Identifying observations Found in Set B but not found in Set A

Re: ODS HTML: Just the file, please.

Using macro variables for date timestamp sql pass-thru to DB2

Re: Emailing the contents of the program editor window

Re: Join across different librefs

Re: Checking condition by "looking forward in future observations"

Macro Variable

Checking condition by "looking forward in future observations"

Re: Reg:Shell X command.

Select only the highest-ranked in each ranking group using the Rank co...

ODS PDF mixing proc report and proc gplot

ODS Templates and Styles Question

ODS Templates and Styles Question

macro to extract text?

Re: macro loop

macro loop

Re: 2 Different Table Styles from a Single CSS Stylesheet: Possible?

2 Different Table Styles from a Single CSS Stylesheet: Possible?

Re: applying format with superscript in SGPLOT

Re: width of BOX around NOTE in GCHART