About ArtC

Astounding · ‎11-04-2015

The program that you have is a good match for the data you have shown. You would run into a problem if your program were different. for example: input dob $10.; That would read in the extra character that you are seeing. But this would be fine: length dob $ 10; input dob $; Another place you could go wrong is by adding an informat: informat dob $10.; But what you have posted is a good match and should be working.

SGK · ‎09-16-2015

Brilliant!

ArtC · ‎02-11-2015

This was the piece that I was missing. Thank you Peter. I do so enjoy learning from y'all and there is so much to learn!

AndrewHowell · ‎11-18-2014

My suggestion (before forking out for guides, training, etc): Each Certification recommends specific training courses (and if training is your thing and you want to pay for it, then excellent. I'm also a SAS trainer, by the way.) Base Certification recommends knowledge equivalent to the Prog1 & Prog2 training courses; Advanced Certification recommends Prog3, Macro & SQL. However, training is not a pre-requisite; you could learn your own way. So look at the agendas for each training course; some of it you will know already, other stuff you will have to go & learn and/or practice, or buy the Prep Guide, or do a training course. But at least it serves as a list of what you need to know in order to pass certification. Good luck!

art297 · ‎04-07-2014

I'm not even going to try and guess what you were searching for.

Ksharp · ‎06-25-2013

NULL, Don't be offended ! Yours is good if csv file is small . Regards Xia Keshan from China

Peter_C · ‎03-29-2013

If you pass a date formatted as monname to excel through ods tagsets.excelxp you can get excel to present it as a month name with the excel format "mmmm". If you use "mmm" you get the effect of sas format monname3. peterC

Reeza · ‎04-03-2013

Start a new thread and clarify your questions please.

ArtC · ‎03-25-2013

Yes the ~ is another symbol for not. In addition to the word 'not' you can also use the ^ symbol. On the mainframe this symbol looks different but is still the shift-6 key. Some languages use <> or >< for variations of not equal. These two combinations have different meanings in SAS and IMO should be avoided.

SASstudent2013 · ‎03-25-2013

Thanks everyone for your replies. I've updated the code based on your feedback and it worked perfectly. One issue is that I had 231 as the number of variables when it should have been 232.

pawan · ‎09-25-2013

Hi Art, I'm too facing a similar issue. Although I divert the output to XML still I get a prompt (window named as File Download) whether to Open or Save or Cancel. Is there any option like NoPrompt or open_excel="no"? I'm using sheet_name=" " option as I got to load data into multiple tabs. ODS TAGSETS.EXCELXP FILE ="C:\.....\FILENAME.XML"; TITLE " Title for 1st sheet"; ODS TAGSETS.EXCELXP OPTIONS(SHEET_NAME="SUMMARY" EMBEDDED_TITLES="yes" ABSOLUTE_COLUMN_WIDTH='10,15,8,....'); Proc Steps.... TITLE " "; TITLE " Title for 2nd sheet"; ODS TAGSETS.EXCELXP OPTIONS(SHEET_NAME="DATA" EMBEDDED_TITLES="yes" ABSOLUTE_COLUMN_WIDTH='10,15,8,....'); Proc Steps.... TITLE " "; ODS _ALL_ CLOSE; Look forward for your valuable suggestions, Pawan

ArtC · ‎03-25-2013

I am going to take a guess at what you want here. Take a look at the WHERE data set option. This option allows you to subset the data so that only the portion needed is used. proc freq data=sashelp.class(where=(name<'M')); table sex*age; run;

art297 · ‎03-21-2013

AllSoEasy: I don't think you got the message. You didn't have an apostrophe in the comment you showed and, if if you did, the /* */ type of comment would not have been bothered by it. You likely have a different problem, like an embedded apostrophe in one of the other not recommended (for a macro) comment types, or an incomplete set of /* */ comments. I would suggest changing all of your comments to the /* */ type, leave the questioned comment in your code and make sure that the code runs. Otherwise, you risk the possibility that an essential line of code is being ignored.

ArtC · ‎03-15-2013

It has been my experience that storing quotes with a macro variable is very very rarely either necessary or a good idea. You can always add them when needed at resolution time. We cannot see what your &MYDATE contains, but the code indicates that it is a SAS date value and not a date form as is &XCESINT. %let mydate = 18945; %let mydate2 = %sysfunc(putn(&mydate,yymmddn8 )); %let xcesint = %sysfunc(intnx(year,&mydate,-1,end),yymmddn8.); %put &mydate2 &xcesint;

PGStats · ‎03-14-2013

An alternative would be : proc rank data=myData out=want; BY SOLD_TO_ORG_ID DELIVERY_YEAR; var delivery_week; ranks new_column; run; PG

Online Status	Offline
Date Last Visited	‎06-20-2021 07:11 PM