>Hi everybody,
>
>Interesting problem http://forums.asp.net/p/1367302/2845866.aspx#2845866 and limno's solution.

Naomi,
But there is a problem there, which made me think none of the solutions is right. Ordering by DateMade which sounds to be a datetime value. In that case if on a given DateTime there could be 2 or more entries then which one is the last? SQL server doesn't make a guarantee on which one would be returned from call to call. That mightr be considered as an incostinecy then. Supposing DateMade could be used to uniquely identify rows then a solution like this might be better:

select TwitterID, Twitter, DateMade
    from Tweets t1
    inner join 
        (SELECT min(DateMade) as fDate, max(DateMade) as lDate FROM Tweets) t2
    on t1.DateMade in (t2.fDate,t2.ldate)

Cetin