First and Last seem to be working backwards

[JohnLouisWood]

I am working with a couple of queries. When I try to find the first value, I get the last value, and vice-versa.
This is not just happening with the queries that I am showing, but seems to be happening 'always' with the other sets/copies of queries that I am working with.
Here is the SQL for query v4:
SELECT Res_15cws_v3_Query.Total15ws, First(Res_15cws_v3_Query.Max_cws) AS F_Max_cws,
Count([Res_15cws_v2_Query]![CountY]) AS Cnt_Max,
First(Val(Res_15cws_v2_Query.FallY)) AS Fir_Fall,
First(Res_15cws_v2_Query.FallN) AS Fir_End,
Last(Res_15cws_v2_Query.FallY) AS Lst_Fall, Last(Res_15cws_v2_Query.FallN) AS Sec_End
FROM Res_15cws_v3_Query, Res_15cws_v2_Query
WHERE ((([Res_15cws_v2_Query]![CountY])=[Res_15cws_v3_Query]![Max_cws]))
GROUP BY Res_15cws_v3_Query.Total15ws;

[JohnLouisWood]

Guci (Vlad) suggested using MIN and MAX instead of First and Last. It seems to solve this problem.

[Minty]

First and Last are (IMHO) virtually useless function is Access SQL.
They really don't do what people expect them to do, and can easily return completely arbitrary results. I'd remove them!

[Welshgasman]

First and last depend on the order of the data?