perdir minhas fotos onde posso encontra-las.

S

selma

De: "James A. Fortune" <[email protected]>
Assunto: Re: need guidence in a big way
Data: domingo, 17 de agosto de 2008 23:51

Jr said:
I need to make a database for my local pool league to keep statistics. I
sat down and went over again in my head what data I have to input and
what data I need to have on output.



INPUT:

Players (First, Last Name) (only one time when they join league)

Teams (Team Name, Venue) (only one time when they join league)

Venues (Name, Location, Phone) (only one time when they join league)

Sessions (Name, Start Date, End Date) (between each session)

Player Results (Games won, Points) (weekly)

Matches (Date, Home team, Away team, Venue) (between each session) &
(weekly)

Team-Players (TeamID, PlayerID, SessionID)



OUTPUT:

Player Standings

Team (Id, Name)

Player (First, Last name)

Win (Sum Total)

Loss (Sum Total)

Points (Sum Total)

Average (Win / Games)

Rating (Points/Games) True Rating

Handicap (+1 or -1 >< 6.5)

Match Rating (Rating + Handicap) (only needed to calculate team handicap
when inputing players into scoresheet)



Team Standings

Team (ID, Name)

Weeks (Date COUNT? from schedule)

Rounds Won (After Handicap)

Rounds Lost (After Handicap)

Points (Sum Total) (with Handicap included)

Games Won (No Handicap)

Pct % (Rounds Won / Rounds)



I know the League Operator wants to spend as little time as possible
entering data, so I sure hope the Access gurus have a few tricks up
their sleeve for me.



Thanks so much for all the help.

Jr.

Here are some things to think about:

1) The input form should look very much like the scoresheet. Use
comboboxes to pick the players. The teams and match date should preexist.

2) Setting up a good match schedule takes as much of a database as the
one for entering scores and printing player and team standings.

3) Players might switch teams partway through the session.

4) A player might play twice in one night if the team is short a player.

5) Putting the schedule and standings on the internet saves a lot of
printing.

6) Once the schedule is set up it is possible to have tables ready for
accepting the results for matches played in any order or on any makeup date.

7) Teams are amorphous. A team should only have scope for a session.
Some leagues force a team to be broken up if they win first place a few
times in succession but other than that a team identity only makes sense
within a session.

8) A venue can have more teams than they have tables. The scheduling
problem can become quite interesting, especially if about half of every
team's matches are at home.

James A. Fortune
(e-mail address removed)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top