>
Leaving TOP n out of it for the moment, I can see few reasons for either the data layer or business logic to care what order the data is in. Therefore, it's something displayed for the user's convenience, so it should be in the user tier.
>

That may be your opinion. I want to see where something authoritative on n-tier design mandates this... Can you provide that...????

Typically, you get into trouble when the word SHOULD creeps into your reasoning.


<<
If it _is_ relevant for the business tier, the business tier should be insuring that the data is in the correct order anyway, instead of relying on the database -- as you said, user requirements change.
<<

I think it is safe to assume here that ordering in this context is a UI oriented feature.

FWIW, I don't think you are far off. My earlier question to you was how would you solve the problem - and be n-tier in nature.

Personally, I don't give a crap about authoritative cites for what n-tier is/is not. It is more an argument of religion. Kind of like what is OO and not OO. I don't engage in those discussions anymore as they are a waste of time.

Rather, instead of saying what is/is not n-tier Garrett - tell me how - using an n-tier philosophy - you would solve this problem when SP's are involved..

< JVP >