09-22-2016 03:35 AM
Under Enterprise Guide 7.11 (22.214.171.12411) 64 bit, with WIndows 7 SP1.
I'm using the following sas macro:
informat &factor._C best12.;
proc univariate data=input;
histogram &factor._C/normal(noprint) cbarline=grey;
It worked properly, but in the log, it returns me the error with the wrong column (compared to the original dataset input).
the observation's column was 257 (which has the issue), but the log of the macro returns my column 27 (which doesn't have an issue).
So, why does this macro change the order of my observations? Or does the macro change the order in general?
09-22-2016 03:52 AM - edited 09-22-2016 03:52 AM
You are inconsistent in your question.
Do ask about the order of the columns, or the order of the observations?
Creating a new variable in a statement after the set statement will have this new column appear last within the observations, naming it before the set statement will put it first in the PDV and therefore in the output dataset.
A simple data step like yours will not change the order of observations.
09-22-2016 04:06 AM
Sorry about the messed up, I'm always a little bit messed up with the rows/columns with the observations/factors.
And yes, I'm asking about the rows/observations.
I was wondering if this is because of the default ASC/DSC options with the new factors created in the macro?
Will this changed the order of my observations?(Since I added one new factors for all observations)
09-22-2016 04:12 AM
So, the question is, which ERROR are you getting?
And can you supply some test data (in a data step) so we can reproduce the behaviour?