Okay, I don't see it.

I'm responsible for setting up a scoring system for our league.

The scores are simple.

Every week, each person can score between 0 and 480, and we run in 12
week quarters, with 4 makups at the end of each quarter. You can only
have 8 scores in a quarter.

So far so good.

The problem is that we only take the best six scores of each quarter, so
out of eight scores for each person for each quarter, only the best six
count.

If you run one record for each person for each session, then you have to
first build a list of people who showed up and played that quarter, then
you have to build a list of scores they made, (might be any number from
1 to 8) and then you have to isolate the best six scores, and add them
up.

When a spreadsheet looks easier, I know I'm doing something wrong.

--
"When I have your wounded."*
-Major Charles L. Kelly, callsign "Dustoff",
refusing an order to leave a hot L.Z., July 1, 1964,
moments before being killed by a single shot.

I think your scenario is a good one. Why don't you script it ? It will
do the job for you.
You may complicate it a bit, by adding the quarter in the 'Find' and
'marking' the retained scores. Thus, you keep all the records and you
can still retrieve all existing data either marked or not.
Are you familiar on scripting ?
Remi-Noel

"Jammer Six" <jammer (AT) oz (DOT) net> a écrit dans le message de news:
jammer-B71424.20273929052005 (AT) bl...OT) shreve.net...

Sounds to me like you have two tables (fields indented):

Player
Name
PlayerID

Score
PlayerID
Quarter (Fall 2005, Summer 2005, etc...)
Week (1...12)
Score (0...480)

The two tables are related by PlayerID. Each time a player shows up for
a weeks practice, you create a new Score record. There can be anywhere
from 0...12 of these related records (or is it 0...8?).

I'll expand upon Remi-Noel's idea to mark the top scores. First write a
script to find and mark the top six scores for a player.

1. Go to related records in Scores
2. Sort based on score
3. Mark the top six scores (and unmark the rest). I would create a
field called IsTopScore, set to only take a True/False value.

Now to total the scores. Make a new relationship that will only link a
player to the scores that are marked. I would create a global field in
Players called gTopScore, set to "True", then define the relationship
like so:

Players::PlayerID = Scores::PlayerID
AND
Players::gTopScore = Scores::IsTopScore

You can create a Summary field in Players that uses this relationship
to calculate the total from scores, and it will only use those scores
that are marked.

Hope this helps!

Kevin Audleman

Oops, forgot something important.

The relationship between Players and Scores also needs to be based on a
quarter (otherwise you'll get all the scores the player ever had
recorded).

I would set a global field somewhere called gCurrentQuarter. Use it in
the relationship like so

Players::PlayerID = Scores::ScoreID
AND
gCurrentQuarter = Scores::Quarter
AND
gTopScore = Scores::IsTopScore

In article <1117579120.217201.311310 (AT) g49g2000cwa (DOT) googlegroups.com>,
"audleman (AT) quasika (DOT) net" <audleman (AT) quasika (DOT) net> wrote:

Kevin, thank you very much!

Remi-Noel, thank you, too.

I think I have it worked out, now there's simply a display issue: I'd
like to present the resulting scores in columns, and can't figure out
how to do it.

I'd like to present every player as a row, and every date as a column.

Thanks again!

You may go to Layout Mode / Layout Setup / Print Options / Print in "n"
colums.
It will look fine in Preview mode only or when printed.
Remi-Noel

"Jammer Six" <jammer (AT) oz (DOT) net> a écrit dans le message de news:
jammer-9ECB95.19412111062005 (AT) bl...OT) shreve.net...

In article <42abc709$0$4909$636a15ce (AT) news (DOT) free.fr>,
"Remi-Noel Menegaux" <rnmenegaux (AT) free (DOT) fr> wrote:

That doesn't present every date as a column, particularly when a player
misses a date.

The only way to break scores out by date or by player that I see is with
a sub-summary part, and they break vertically, not horizontally.

Okay, here's my stab at your problem.

I assume you mean all the scores for the current quarter. This is not
entirely straightforward, as those scores are records in a related
table (this is one of those cases where a 'flat' spreadsheet file would
make things simpler).

What you'll do is create a series of portals displaying the score
field, each with only one row, sorted on date. Change the 'starting
row' field in the portal setup dialog to display the successive weeks.

To get the correct records, use the relationship defined above based on
CurrentQuarter.

Let me know if that works.

Kevin