02-27-2023
Fugue
Quartz | Level 8
Member since
07-25-2012
- 318 Posts
- 29 Likes Given
- 1 Solutions
- 118 Likes Received
-
Latest posts by Fugue
Subject Views Posted 2886 09-22-2021 05:34 PM 2980 09-21-2021 01:45 PM 3084 09-20-2021 06:14 PM 3129 09-20-2021 05:44 PM 3888 10-05-2018 02:49 PM 3893 10-05-2018 02:30 PM 3960 10-04-2018 05:24 PM 3975 10-04-2018 04:32 PM 1852 08-01-2018 03:28 PM 1853 08-01-2018 03:24 PM -
Activity Feed for Fugue
- Got a Like for Re: US county-level map. 01-09-2025 11:32 AM
- Posted Re: replace every value of a variable with another randomly selected variable on SAS Programming. 09-22-2021 05:34 PM
- Liked Re: replace every value of a variable with another randomly selected variable for Kurt_Bremser. 09-22-2021 05:34 PM
- Liked Re: replace every value of a variable with another randomly selected variable for Reeza. 09-22-2021 05:31 PM
- Liked Re: replace every value of a variable with another randomly selected variable for Kurt_Bremser. 09-22-2021 03:09 AM
- Posted Re: replace every value of a variable with another randomly selected variable on SAS Programming. 09-21-2021 01:45 PM
- Liked Re: replace every value of a variable with another randomly selected variable for Reeza. 09-20-2021 06:45 PM
- Posted Re: replace every value of a variable with another randomly selected variable on SAS Programming. 09-20-2021 06:14 PM
- Liked Re: replace every value of a variable with another randomly selected variable for Reeza. 09-20-2021 05:47 PM
- Posted replace every value of a variable with another randomly selected variable on SAS Programming. 09-20-2021 05:44 PM
- Got a Like for Re: character date to Date9.. 11-13-2019 05:56 AM
- Got a Like for Re: character date to Date9.. 12-18-2018 04:12 PM
- Posted Re: SAS 9.4 fails after uninstalling 9.3 on Administration and Deployment. 10-05-2018 02:49 PM
- Posted Re: SAS 9.4 fails after uninstalling 9.3 on Administration and Deployment. 10-05-2018 02:30 PM
- Got a Like for SAS 9.4 fails after uninstalling 9.3. 10-05-2018 10:45 AM
- Posted Re: SAS 9.4 fails after uninstalling 9.3 on Administration and Deployment. 10-04-2018 05:24 PM
- Posted SAS 9.4 fails after uninstalling 9.3 on Administration and Deployment. 10-04-2018 04:32 PM
- Posted Re: SAS and Office interoperability on Microsoft Integration with SAS. 08-01-2018 03:28 PM
- Posted Re: SAS and Office interoperability on Microsoft Integration with SAS. 08-01-2018 03:24 PM
- Posted SAS and Office interoperability on Microsoft Integration with SAS. 07-20-2018 03:18 PM
-
Posts I Liked
Subject Likes Author Latest Post 3 1 1 1 1 -
My Liked Posts
Subject Likes Posted 1 01-17-2014 08:32 PM 1 10-04-2018 04:32 PM 1 01-20-2014 04:04 PM 3 06-17-2014 07:18 PM 3 07-26-2013 06:28 PM
08-13-2015
02:34 PM
@ ballardw . . . we rem'd out the style=PrinterListing command and this seems to have resolved the issue with font sizes being too large. Thanks for pointing me in that direction.
... View more
08-13-2015
02:31 PM
@Cynthia . . . further to my earlier reply, I replaced the logo with one that is 150 DPI and sized appropriately. This seems to have resolved the logo issue. Thank you for pointing me in that direction.
... View more
08-07-2015
09:24 PM
@ Cynthia . . . after perusing those papers, it seems that the authors are saying that (for ODS PDF output, at least) DPI determines image size when PREIMAGE is used in a title/footnote statement. This appears to be confirmed according to this paper by Scott Huntley and yourself: http://www.mwsug.org/proceedings/2014/SS/MWSUG-2014-SS03.pdf. Refer to bottom of page 23 - 25. The recommendation seems to be to ensure graphics for ODS PDF have a DPI=150.
... View more
08-07-2015
08:19 PM
@ Cynthia . . . Thanks for those links. I'm reading them through and will let you know how it goes . . .
... View more
08-07-2015
08:18 PM
@ballardw . . . Good catch on the "printerlisting" style. I was in such a hurry to answer my specific issue that I completely omitted to consider that this style may have been a custom style or one that was not included in 9.3. The contractor ramming through the migration should have considered this, of course. Obviously, we are now forced to deal with our style templates!
... View more
08-07-2015
05:38 PM
We have many reports that include the company logo at the top of each page using the TITLE1 and PREIMAGE technique as follows . . . ods listing close; ods escapechar='^'; ... more SAS statements . . . %let style = PrinterListing; %let outfile = "some output path\some file name.pdf"; ods printer pdf startpage = no sas file = &outfile uniform notoc; title j=l '^S={preimage="our logo path\our corporate logo.jpg"}'; . . . more SAS statements In SAS 9.1.3, the logo appeared "just the right size" in PDF. After moving to SAS 9.3, the logo appears too large. (In fact, all of the text and graphics elements in PDF output in SAS 9.3 appear larger than under SAS 9.1.3.) I've searched the forum and the internet for a solution. Unfortunately, I haven't been able to find anything with an obvious answer. Anyone ideas?
... View more
07-30-2015
03:01 PM
My reply is not intended to be a comprehensive overview of fuzzy matching. There are lots of SAS samples on the internet. Soundex was designed by genealogists to deal with differences in spelling of names. It doesn't handle numbers well (for example, 1 is not interpreted as ONE, both 112 and 1122 are simply treated as numbers so the soundex function will miss the similarity entirely). It doesn't expand abbreviations (AVE is not expanded to AVENUE, FT ST JOHN is not interpreted as FORT SAINT JOHN), or vice versa. So, soundex will work reasonably well on some variables (e.g. City or State), but less well on variables such as Street. However, some data cleansing may be required prior to attempting a match (e.g. ensuring State names are all abbreviated or vice versa). There are other SAS Functions that can help with fuzzy matching, and that may be superior to soundex depending on the situation. (Example: http://blogs.sas.com/content/sgf/2015/01/27/how-to-perform-a-fuzzy-match-using-sas-functions/)
... View more
07-29-2015
09:31 PM
data have; input name $ 1-2 invoice_datechar $ 5-20 ; format invoice_date datetime.; invoice_date = input ( invoice_datechar, anydtdtm.); datalines; A 2014-02-12 20:12 B 2014-04-01 19:00 D 2014-05-03 23:31 E 2014-07-29 17:10 R 2014-09-15 10:31 F 2015-03-10 12:12 G 2015-06-02 21:18 GF 2015-06-09 10:13 DF 2015-06-27 15:11 ;;;;; run; data want; set have; format invoice_yearmonth YYMON7. invoice_quarter qtr1.; invoice_year=year(datepart(invoice_date)); invoice_month=put(datepart(invoice_date), monname3.); invoice_yearmonthchar=compress(put(datepart(invoice_date), monname3.)||'-'|| invoice_year); invoice_yearmonth=datepart(invoice_date); invoice_quarter=datepart(invoice_date); ; run;
... View more
07-29-2015
03:28 PM
Apparently, I am blind. How many times did I read that documentation? Thanks, Jos and Marie.
... View more
07-29-2015
02:18 PM
Thanks, Marie. Are you able to point me to the documentation stating that AMO 6.1 works with SAS 9.3? I have searched everything I could think to search, and could not find it . . . A drawback to the way the forums are currently designed is that I can only mark two replies as "helpful" and only one response as "correct." So, I was forced to mark your comment as "helpful" rather than correct. Partly my fault, for putting more than one question in the same discussion thread. Interestingly, IE 11 (running on Windows 7 x64) did not allow me to see the Helpful and Correct Answer buttons. I can only see them in Chrome.
... View more
07-24-2015
06:09 PM
Is the code in your first program wrapped in a macro? If so, the enddt macro will be local unless you expressly declare it as global.
... View more
07-24-2015
05:32 PM
I missed that you were responding to the OP. Gotcha - just having a conversation here - hope I'm not coming across as adversarial or critical. I've been off forums for awhile, just back, and trying to re-engage.
... View more
07-24-2015
04:59 PM
I get that - it looks like it is some type of transactional data on its face. But my question is why keep the OBS if it isn't needed? Just gettiing back to basics . . . simpler is better. Now if the OP wants to keep OBS because it is important to further analysis, then fine. But, the data is not necessarily structured in such a way as to know whether subsequent events relate to prior events. We certainly don't have the business context to know. We are assuming based on limited information. Further, in the example provided, the OP wants to keep OBS 1. Sequentially, however, OBS 2 appears to be a reversal of OBS 1. So, shouldn't OBS 3 be the row to keep if OBS is important?
... View more
07-24-2015
03:31 PM
Comment to push this . . . Question #1 still not answered. Anyone?
... View more