Congratulations to your first solution then ... but could at least spear Toms posting a like. 😉 ... View more

@Tejaswini3 wrote: Without transpose statement, pls write code to solve Why is that? Than you needed to detail your problem a bit. ... let's say just to motivate people. 😉   Err ... being with it: My observation is that you keep on asking the same questions over and over (e.g. here and here ). You got answered there, though you have neither marked these threads as solved nor detailed what was missing to an acceptable solution. ... sooo, could you help us a bit, please? ... View more

Hello Beverly! First off thank you for sharing this piece of information. In response to your question about the sensibility of a "distance to next rank" indicator I would like to utter my doubts. Wouldn't such an indicator result in people to overdo posting and liking just to gain the next level? I personally would like to see that measure being kept secret as I "guess" that this guides people to deliver quality focused contributions and highlighting such postings with likes. Having said this I would like to add that the disclosure of the required tenure could be helpful to get an idea of the level groups. This could render a motivation for regular participation. Just my 2ct Regards Fja ... View more

Well, as nobody has answerd yet. Wilde guess: the pathes are messed up. Could you please open the frame.html in a text editor ... (like vim :D) and see, what pathes are used to load in the individual parts? ... View more

As a rule of thumb if the column is unambigous you do not have to qualify the table using a qualified name. If there is some ambiguity (eg. both tables contain a column called bla) you have to use the a.bla ... to specify the column to select.   Maybe you have a little play in SAS and try it yourself:  data work.TestData1; input ID A$ B$ C$ bla$17.; datalines; 1 a1 b1 c1 bla1_fromTableOne 2 a2 b2 c2 bla2_fromTableOne ; run; data work.TestData2; input ID D$ E$ F$ bla$17.; datalines; 1 d1 e1 f1 bla1_fromTableTwo 2 d2 e2 f2 bla2_fromTableTwo ; run; proc sql; select A, B, C, D, Two.bla from TestData1 as One, TestData2 as Two where One.ID = Two.ID; quit; run; --fja   ... View more

Hello!   Though I completely agree with Kurt's answer above, I find this topic intresting enough to add some thoughts.   This is tricky! What you do by the join is that you assemble a new table ... the naming of its columns are derived from the qualified and unqualified names ... or AS expressions if given.  From that, any unqualified name in the select part could origine from any source table and is not determined by the select statement - if given in the form quoted. For short: As @Kurt_Bremser has aready put it, you need to have a look at your data. Now it is that tables happen to change and columns get added form time to time. For that reason my suggestion would be to use qualified names whenever possible. ... but this is of course beyond the question posed.   --fja   ... View more

That resulted in a more sane looking dataset, agreed. It is just that @JLang055 asked for a different kind of output. --fja ... View more

Looks like stacking cols ... this is available as a point and click task in Studio under Tasks->Data->Stack/Split Columns. Generates something like this: data work.TestData; input Col1$ Col2$ Col3 $; datalines; A B C D E F ; run; data work.__tmp__; set WORK.TESTDATA; _Case_=_n_; run; proc transpose data=work.__tmp__ out=work.TestOut(drop=_Label_ rename=(col1=StackedCol)) name=_Level_; var Col1 Col2; by _Case_; run; proc delete data=WORK.__tmp__; run; ... View more

OK, if you just want to have a "clean" intermediary table, than you could use proc sort: data work.TestData; infile datalines dsd; input FID MOOD ANXIETY EAT DEVELOP; datalines; 1, ,1, , 1, , ,1, 1,1, , , 1,1, , , 2, , ,1, 2, ,1, , 2, , ,1, 3, ,1, , 3,1, , , ; run; PROC SORT DATA = work.TestData NODUPKEY out=work.testdata2; BY MOOD ANXIETY EAT; RUN; ... View more

What about defining an index with option unique? --fja ... View more

Hello! Would you like to filter an existing dataset or would you prevent the insertion of superfluous observations? --fja ... View more

Hello Nietsche! Well ... if you use the proc import you should see some (equivalent) data step code being stated in the log using explicit informat statements. You could use that instead to determine informats explicitely (i.e. your date11). Please have a look at the (probably) helpful examples in the documentation online. As far as I know, there is no way to control the informat using the proc import directly. --Fja   PS: I am suffering a bit from a hangover ... appologies for me English ...  ... View more

Hello, does RATING contain the expected rating string? I.e. Have you output it via put or the like? --fja ... View more

The WHERE statement filters / selects observations that meet a certain condition. In this case it filters any observation with a variable that contains the "segmento" argument of the macro. ... View more