About Cynthia_sas

DanH_sas

I believe the issue here is that you've create a lattice that is four cells high and one cell wide, but your set the the designHEIGHT to be a small 640px and the designWIDTH a lot larger. This setting probably prevents the graph from drawing due to space. Try swapping your designwidth and designheight values and see if you get the graph to appear. Hope this helps!

filippo_kow

Hi all, Thanks a lot for your support! It works perfectly 🙂 Just one remark, maybe it will be somehow useful for other people. When run the stored process from SAS Add-In (not using ods excel) we need to use proc report (instead from proc print). Thanks again! Filip

Tom

Yes. The WHERE statement is processed like an SQL statement. And in that setting the functionality implied by the ?? modifier does not exist. Also are you positive the character variable has a maximum length of only 8? If not then you use of a width of 8 on the informat will ignore the end of the string. Unless there is some reason you want it to ignore the ends of the string use the maximum width that the informat supports, which is 32. The INPUT() function does not care if the width of the informat specification is larger than the length of the string being read.

Cynthia_sas

Hi: That paragraph mark is being displayed in your Microsoft Word because of the RTF control strings created in the RTF file. You can simply go into Word and look for the Show/Hide marks button on the Word menu to turn off the display of the paragraph symbol. As far as I know, 0D0A is the hex code for carriage return/line feed and is not necessarily the same as the code generated inside the RTF. I think that usually the RTF string for a paragraph is \par or \pard...you'd have to look in the RTF. But I don't usually recommend post-processing the RTF control strings because Word is very touchy if you mangle the RTF and then it won't display the file. Cynthia As an example, here's a simple display in Word of an RTF document. The Hide/Show Marks button was turned on in Word. And that is just a small snippet of the RTF file.

Kurt_Bremser

LibreOffice supports all MS Office formats, so you should use the XLSX engine.

ddutton325

Thanks so much Cynthia! That explains why I couldn't find it in the documentation. I shall spread the word that we should modernize our code to use the current function-style syntax.

Cynthia_sas

@PaigeMiller -- I agree with you. If someone is not comfortable with PROC REPORT and using helper variables and COMPUTE blocks, then pre-summarizing and computing the percents in a DATA step or switching to PROC TABULATE (which has custom denominators and also the ROWPCT/COLPCT statistics) is a preferred approach. For the sake of completeness, here's an example of how to do it within PROC REPORT using helper variables. I switched to using SASHELP.SHOES because the OP did not provide data. This report has a percent of region and then a fake percent where the denominator was set to a constant value of 3371. Ths places where the 2 new percents are calculated are highlighted: Basically, if you want to calculate percent of region with PROC REPORT, you have to "grab" and hold the count for that region into a helper variable called RCNT, which is automatically retained and then use rcnt in the divide for REGPCT. The calculation for FAKEPCT just uses a numeric constant as the denominator. Cynthia

Cynthia_sas · ‎09-20-2024

HI: Well, that is not what I thought you were doing with gradients. I find that extremely hard to read, especially with the colors in G and H blurring together. However, I think this is a question you'd need to ask of Tech Support. The only way I know to "touch" the Excel cells with things like Excel-specific number formats is with the TAGATTR style override. However, I don't understand how Excel defines the gradient for the cell or whether it would be possible in a TAGATTR. Cynthia

tom_grant · ‎09-18-2024

You can upload your project files using SAS Studio - this will be a bit of a pain because you can only upload files (& not entire folders) so you'll have to repoduce the folder structure of the EM project. If you are just concerned about the diagrams, you can save those as XML, upload to Ondemand, & then import in EM.

Tom · ‎09-16-2024

In your macro call you asked the macro to put the count into a macro variable named SALESCOUNT. If you want to use SALESCOUNT after the macro ends then make sure to define it BEFORE calling the macro. %let salescount=unknown; %counts(userid, salescount, customers) %put &=salescount; You named the parameter COUNT, but I would think a name like MVAR or MVARNAME would have been better. It would make it clearer how the parameter is going to be used. You can make the macro smart enough to force the macro variable into the global symbol table when it does not already exist. %macro counts (varname, mvarname, dsname); %if not %symexist(&mvarname) %then %global &mvarname; proc sql; select count(distinct &varname) format=32. into :&mvarname trimmed from &dsname; quit; %mend counts; %counts(dsname=customers,varname=userid, mvarname=salescount)

FernaNino · ‎09-06-2024

Hi Cynthia. I did it. I realized which semi-colon was in the wrong place. Thank you!!

ballardw · ‎09-06-2024

You will want to make sure that the path for the library location starts at Drive (windows) or disc mount point or root of your access. If the path does not specify such then you would get a path relative to a possibly changing disc location, such as where SAS is executing, and not where you intend. Also you need to have permission to read that location and if you want to create data sets write permissions. If your SAS session is running from a server the path needs to be as the SAS server sees things. Which means that it may not see your local hard drive.

OliviaOk · ‎09-04-2024

Thank you for the help.

tgleghorn · ‎08-26-2024

creating the dummy worked. now just have to limit it to the one cell 🙂

Cynthia_sas · ‎08-22-2024

Hi: If you're going to use ODS TEXT, and you want to change the style from the default placement I believe you need to change the style template used for the output. There's an example of doing this in the documentation https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/odsug/p14gx25pepks6dn1q9m7vkq3gfoi.htm#n0rx93bn3orev5n1ogar2yb813kra Cynthia

Online Status	Offline
Date Last Visited	yesterday