SELECT g.golfername, g.gamedate, g.score FROM golferstats AS g WHERE 3 > (SELECT COUNT(*) – 1 FROM golferstats WHERE g.Score IS LESS THAN OR EQUAL TO Score AND g.golfername = golfername);

SELECT g.golfername, g.gamedate, g.score FROM golferstats AS g WHERE 3 > (SELECT COUNT(*) – 1 FROM golferstats WHERE g.Score

Jamie.

–

Not saying this is Best Practice, but it’s a very easy guideline that always worked for me.

I put lots of consideration into the table layout, after some painful experiences from some years back. Lesson learnt:
Database basics is pretty easy and fun. But for a person “coming from spreadsheets” there is an extremely important difference: You can rework, sculpt, redesign, reprogram a spreadsheet solution until it’s really good, but a database must be right from the very beginning. If not then it grows useless and you must choose between a total rebuild or some really ugly workarounds.

Best wishes Harald

In Oracle this would be a correlated subquery.

I haven’t used Access all that much at the SQL level – wasn’t quite sure what to expect.

I’ve got a table called golferstats with three columns:
golfername, gamedate, score
This selects the previous 3 scores per golfer

select g.golfername, g.gamedate, g.score
from golferstats as g
where g.gamedate in (select top 3 t.gamedate
from golferstats as t
where t.golfername = g.golfername
order by gamedate desc)

Rob

Z: Hello, kettle? This is pot. You’re black.

Dianne: I tried using TOP, but couldn’t get it to work. I wanted every player to show up in the query, not just one. If it was just one, that would work, but I would need one query per player. Can you change that SQL to get rid of the WHERE clause and show the TOP 3 orders for every customer? So if you had 10 customers, it would return 30 records?

Ross: Did you forget the smiley? I think .net would be like using an industrial strength nail gun to hang a picture (but I’m speaking from a position of zero authority on the subject).

At times, I too face doing it the “right” way or the “dirty hack” way…

I get really annoyed with situations where I’m forced to do a dirty hack just because the pressure is on.

You’ll never regret having built a solution the right way.