Enterprise Guide always runs on Windows. But the SAS code you submit via EG could be running on some other operating system.  You probably need to make sure that the machine where SAS is running can run Excel. ... View more

Thing is I'm not allowed to change the VBA tool, I don't have the rights, I'm just creating the input file that is compatible with the tool. I would share it but I don't have the rights ... View more

@polpel wrote: Hello,   .So here's my issue: I've got a TABULATE procedure that gives me two variables called 2017 and 2018. Seriously doubt that Tabulate creates variables of those names. Possibly shows that as a value for a variable but the variables that Tabulate creates would have a statistic name suffixed to an existing variable.   If you have two variables that contain those values then you may be not using Proc Tabulate to the best advantage.   One might suspect that you are doing something related to dates but not actually using SAS date values then a proper format would display the dates with the year as wanted without playing around with variable names(?).   Code. Example input data. Where the 2017 and 2018 have to change to possibly 2015 and 2016.   Instructions here: https://communities.sas.com/t5/SAS-Communities-Library/How-to-create-a-data-step-version-of-your-data-AKA-generate/ta-p/258712 will show how to turn an existing SAS data set into data step code that can be pasted into a forum code box using the {i} icon or attached as text to show exactly what you have and that we can test code against. ... View more

Hello, This method seems to work only with mains that are paired with a main, which means that all mains who don't have a sub are "dropped"... ... View more

Your have data violates your rule, as num_fam=126 has only one observation: data have; input num_fam num_sub val1 val2; cards; 123 1 75 0 123 2 0 12 124 1 14 0 124 2 0 5 125 1 10 0 125 2 0 10 125 3 16 0 125 4 0 10 126 1 14 0 ; If that happens in the middle of the dataset, it might invalidate solutions that expect an even number of observations for every num_fam. ... View more

Add one more option PRINTMISS:   proc tabulate ......... class ......./missing ; table ........../ printmiss ; run; ... View more

Try some style.   ods excel ... proc report .... ......... define xx / style={ tagattr="wrap:no"} ; .......... ... View more

@polpel: There're no fewer than 20 different methods of doing this in SAS. @Reeza has shown you one, perhaps the simplest. If you have a "huge" base table and a rather short reference list, an inner join could be better since, unlike the @Reeza's subquery, it can hash the list and look it up for every row in the huge table without sorting the latter.     Another option is to stick the keys from the reference table in to a hash table in memory and look it up for every record from the base table in the DATA step. If your reference list is static and you're going to search it often, perhaps the best option is to create an in/format using the reference file's keys as the in/format input with something like 1 or "1" as the in/format response. Then the in/format can be used in the WHERE clause, be it the DATA step or SQL.   Show samples of your two files, and you can be assured that plenty of folks here will show you concrete ways of how any of the above (and more) can be done.   Kind regards Paul D. ... View more

data have; input groupnumber $ numberingroup; datalines; group1 450 group2 256 group3 214 ; proc transpose data=have out=want(drop=_:); id groupnumber; var numberingroup; run; ... View more

That last proc tabulate reverses cols and rows,   the first one was: "table type,N;" the newer one is "table N,type".   If you need "transposed" dataset then use proc transpose ( https://documentation.sas.com/?docsetId=proc&docsetTarget=p1r2tjnp8ewe3sn1acnpnrs3xbad.htm&docsetVersion=9.4&locale=en 😞   proc tabulate data = tmp output = tmp2(keep = type N); class type; table N, type; run; proc transpose data = tmp2 out = tmp3; var N; id type; run;   All the best Bart     ... View more