Yes, I'm all set now. I enabled scripts for sas.com and it works. Thanks! ... View more

I see the problem. I have a security plug-in for Firefox called NoScript, it works when I set this to its lowest security level, but not when I set it to the highest security level. ... View more

This is not working in Firefox 143.04 on Windows 11. I click the check box and the web page doesn't change, it still shows the "non-discussion" topics. ... View more

I think we need to see the code that creates data set MYMAP. Please post code in the proper code box (it has the little running man icon) as you did in earlier threads. ... View more

I agree with QBF, there are a lot of things in your code and problem statement that either don't make sense, or need a lot more explanation, or raise eyebrows. I'm not at all sure your question is the one I gave a solution for — is the problem really that you want cyan lines but you never told SAS to draw a cyan line? I think it would be a positive thing to re-write this whole problem statement with a goal of making it much clearer. And don't make the mistake of assuming that we know what you are doing or we can figure out what you are doing, because as I said, I have no idea what data set _test_mm_ind is doing or why it is even included. ... View more

Nowhere in your code do you ask for a CYAN colored line.  This should work, I'm too lazy to fix all of your lines, I only fixed one line, you can fix the rest of the lines as needed.   refline &_ref_2./axis=x lineattrs=(color=cyan thickness=2 pattern=solid);     By the way, it not clear what the data set named _test_mm_ind has to do with anything. You included it without giving an explanation of what it does or why it is important. ... View more

Nesting of %IF statements in open code is not supported   Nested %IF is not supported in open code. The code in red is a nested %IF, in other words an %IF within another %IF. You cannot code this way outside of a macro.   Your code seems like it should run inside a macro. ... View more

The residuals need to be (approximately) normally distributed, not the raw data. The raw data can have any distribution, and if the residuals are normally distributed, then GLM is appropriate.   ... View more

Your very general question can only be answered with very general answers.   You read the dynamic data into SAS, then you use SAS to write to a PDF file in the desired format.   I also suspect that there are tools other than SAS that would be better for this task, but I have no idea what those other tools would be. You might want to ask companies that create bills what they use. ... View more

@ballardw  I hadn't thought about what a use could be for code like "N=%left(&sam)", but if you are right, or if you are wrong, I think there is probably a better way to handle it.   It is a constant struggle to get people to explain the big picture of what they are trying to do, they only want to talk about the specific coding problem they have, they don't want to get into the big picture. This particular request seems like it is an instance of the XY Problem. ... View more

I would add to @LinusH 's request that you should explain in words (not code) what you are trying to do. And why do you apparently want to store SAS code in a data set variable? For example your code includes this:   visit1="N=%left(&sam1)"; ... View more

If ever there was an argument for not writing your own code to do this type of calculation, this thread is it. ... View more

If you have missing values for x, I think you get the wrong answer here when missing values are present, whereas using PROC SUMMARY you get the right answers. PROC SUMMARY gives different weighted means and weighted standard deviations for observation 19 than your program does. So in addition to the difficulty of writing your own formulas, you don't get the benefit of the work SAS has already done (and your company or university has paid for) and you potentially get wrong answers writing your own formulas.   BTW — I think your weighted standard deviations are wrong even when there are no missings, they do not match PROC SUMMARY.   Which is why I strongly advise people against writing their own formulas when SAS has already done that for you and tested it thoroughly.   data _temp; do i=1 to 20; x1=sin(i/10); x2=cos(i/20); x3=sin(i/100)-cos(i/30); x4=sin(i/50)+cos(i/200); wt_x1=10; wt_x2=25; wt_x3=30; wt_x4=35; if i=19 then x4=.; output; end; run; proc transpose data=_temp out=aaa; var x:; by i; run; proc transpose data=_temp out=bbb; var wt:; by i; run; data long; merge aaa(rename=(col1=x)) bbb(rename=(col1=weights)); by i; run; proc summary data=long nway; class i; var x; weight weights; output out=want_weighted stddev=s mean=m; run; proc summary data=long nway; class i; var x; output out=want_unweighted mean= stddev=/autoname; run;         ... View more

Yes, I'm sure it can be done in SQL, but I personally refuse to accept the limitation that it must be in SQL, which then prevents me from using the power of SAS and prevents me from using all the features of SAS. In addition to the reasons I gave for doing this on a long data set and using PROC SUMMARY, if you have code that works for 4 values of x, and then at some point in the future you have more than 4 values of x (like 5 or 6 or 12 or 107 values of x), you have to modify the SQL code, whereas in my code no modification is necessary, even if you have 107 values of x. If you have a lot more than 4 values of x, this modification of SQL would become tedious and error-prone. So, I will stick with my answer. I'm sure someone will come along and provide SQL code to do this. For anyone else reading along, don't do this in SQL, don't make it harder than it needs to be.   The code I gave works if the weights change for every value of i. ... View more