Hi @ballardw,   I was looking for something like what was suggested by Tom. But having said that, I don't find the solution ideal. It is another macro to compile somewhere first.   Plus, we cannot use something like that:   proc sql; select sex_new length=max(lengthn(sex)) from sashelp.class; quit; ... View more

I was looking in the log. But you're right. I didn't notice it. But it looks ok in a text file. ... View more

First of all, thank you to everyone for the time and energy trying to figure things out. Thanks Ballard for the explanations of n= and #.   I've tried both examples with file print as well as with file log and with file pointing to permanent file. RESULTS tab > does not create the line (could be an HTML thing) LOG > work for the first example but not the second one External file > works with both examples   Example 1 1.1 with file print (does not work) 1.2 with file log (works as expected)   1.3 with file test (works as expected)   Example 2 2.1 with file print (does not work as expected)   2.2 with file log (does not work as expected)     2.3 with file test (works as expected) ... View more

I've tried it with SAS OnDemand but get the same issue. ... View more

It's nice to know that the feature has not changed. It is an installation specific issue.   The default value of  the formchar and formdlm options have always been a mess in my installation. I've never been able to fix the issue.   FORMCHAR=‚ƒ„…†‡ˆ‰Š‹Œ+=|-/\<>* Formdlim is equal to a special non printable character by me.   Using the right values doesn't help in this case as I'm not ouputted a table options formchar="|----|+|---+=|-/\<>*" formdlim=' '; But could it be something else in this direction I should look into?   ... View more

Release: 3.81 (Single User) Build date: Aug 4, 2020 11:39:11 AM SAS release: 9.04.01M5P09132017 SAS platform: X64_10PRO WIN ... View more

Hi, First note that you're working with "macro variables" and not "macros". That's two different things. So I would use %let newmcrvar= rather than %let newmacro=.   Second, it is a good practice to add a dot at the end of a macro variable call. You will otherwise face some issues if you have dots in your string e.g. a dot in a filename (myfile.xlsx)   Third, when you use two ampersands one after the other, they are converted to a single ampersand. So, in your case, you currently get "test1" as output but you actually want "&test1." which will be automatically converted to 5000 in the second internal loop. I let you figure out the solution with this extra info. ... View more

Yes, Thank you @AMSAS ... View more