Oxford Croquet Logo
-----------------
-----------------
-----------------

About this Program

The program is written in Visual Basic to run on web servers (i.e. written in ASP). Any computer running Windows can add a local web server from the Add/Remove Programs page, Add/Remove Windows components. You do need to indicate that the server should run ASP. The screen format is designed to suit mini-laptops.

It is not intended that this program is run across the web (although it can be) but installed on the computer used at the tournament. If it is run across the web it could cope nicely with multi-venue tournaments.

The tournament data is stored in MSAccess format in a subdirectory ".\mdb" below where the code files are stored. This subdirectory must be read/write for the web server user. In Folder Options you may need to set "Use Simple filesharing" to off (last setting in list).

Typically the web server will have a directory tree C:\Inetpub\wwwroot. A directory can be made below that, e.g. 'swizz', and the program files decanted into it and the subdirectory .\mdb created (see below). The program is then run through a web browser by accessing: http://localhost/swizz/index.asp.

Program Function Calls

Top level programs

index.asp

Introduction page

menu.asp + (welcome.jpg)

menu.asp

Left hand menu of options

other top level programs

ranking.asp

Routine which iteratively ranks players based on who beat who

 

show_tournaments.asp

Allows the user to open existing or create new tournament

open_tournament.asp
=> make_tournament.asp

show_lawns.asp

Reads the lawns table and allows the user to add or alter lawn details

update_lawns.asp

show_players.asp

Reads the players table and allows the user to add or alter player details

update_players.asp

setup_game.asp

Selects available players not in play, shows viable opponents indicating those who have played before and shows free lawns

make_game.asp
delete_game.asp

show_games.asp

Shows games in play and allows the result to be recorded. Indirect link to show players' results

report_result.asp
=> write_results.asp
(show_player_results.asp)

show_results.asp

List the completed games with details. Indirect link to show players' results

report_results.asp for corrections => write_results.asp

(show_player_results.asp)

show_winners.asp

Gives player statistics. Indirect link to show players' results

(show_player_results.asp)

Secondary Programs

delete_game.asp

Quizes for confirmation then deletes the game and sets the players' and lawn availabilities

 

make_game.asp

Receives who and where and writes them to the games table

 

make_tournament.asp

Create a new mdb file and pre-create lawn, player and games tables

 

open_tournament.asp

reads an existing *.mdb file from ./mdb and writes as session variable

 

report_result.asp

Presents form for winner and result to be entered

write_results.asp

show_player_results.asp

Produces statistics from completed games in the games table. Indirect link to show players' results

(show_player_results.asp)

timeout.asp

If the web session times out - this information page is called to ask user to reselect tournament

show_tournaments.asp

write_results.asp

Updates game result to games table in database

show_games.asp

update_lawns.asp

Writes new/changed lawn details to lawns table

 

update_players.asp

Writes new/changed player details to players table

 

Subdirectory

./mdb

sub directory for tournament data - must be read/write for web user

 

Support Files

favicon.ico

Icon picture for URL

 

footer.asp

Information strip at the bottom of each screen

 

html_tags_1.asp

Include file containing header information, esp. link to style sheet

 

swiss.css

Style sheet for program

 

welcome.jpg

splash image when program opens

 

The code is not pretty or efficient and is not intended to be modifed. Use it at your own risk!

Data Formats

Each tournament consists of three tables; lawns, players and games. Two temporary tables, temp and winners, may appear. These are 'working' tables, should be ignored and can be deleted without affecting the program

Lawns

ID AUTOINCREMENT

index field

lawn_name TEXT(255)

user chosen lawn name

inplay YESNO

flag showing if there is a game in play on that lawn

usable YESNO

flag showing whether the lawn is available or withdrawn from play

comments MEMO

user notes

Players

ID AUTOINCREMENT

index field

forenames TEXT(255)

player details

surname TEXT(255)

player details

handicap FLOAT

handicap

available YESNO

willing to play another game

inplay YESNO

currently playing a game

p_index FLOAT

handicap converted to Index (points)

points FLOAT

live index used in iterations

email TEXT(255)

not used

comments MEMO

user notes

Games

ID AUTOINCREMENT

index field_

ID1 NUMBER

player one index in players table

surname1 TEXT(255)

player one details INCLUDED ONLY TO MAKE TABLE READABLE

forenames1 TEXT(255)

player one details INCLUDED ONLY TO MAKE TABLE READABLE

ID2 NUMBER

player two index in playesr table

surname2 TEXT(255)

player two details INCLUDED ONLY TO MAKE TABLE READABLE

forenames2 TEXT(255)

player two details INCLUDED ONLY TO MAKE TABLE READABLE

IDL NUMBER

lawn index number in lawns table

lawn_name TEXT(255)

lawn name INCLUDED ONLY TO MAKE TABLE READABLE

winner_ID NUMBER

index number of winner in players table

score FLOAT

score

letters TEXT(255)

peels etc.

ontime TEXT(255)

whether game went to time

start DATE

start time of game

finish DATE

time results entered

This program follows in the shadow of ones written by David Maugham and Samir Patel.

Dr Ian Plummer
Balliol College
Oxford
OX1 3BJ

October 2009