Frequently Asked Questions

Q. How does the single user license differ from the club-wide license.

The single user license allows a single, named person to use Rugby Statz.  It is not a concurrent license.  The license can be installed on multiple machines but the license can only be used by the named user.  The license can be transferred to another individual within a club if the original named user no longer uses the application.

The club-wide license allows unlimited use of the application by members of a single, named club.  It is a multi-user license.

Q. I have several players that have played with different clubs during their career. Is it possible to allow a player to play for two or more clubs and how do I set it up?

Most certainly! Although Rugby Statz will enforce that a player be a member of only one club at any point in time, changing that club during or after a season is permitted (as the player moves from one club to the next).

The way to do this is to have only ONE record for the player. This will ensure that career statistics are preserved. Do not be tempted to have multiple records for the player for each club in which he/she plays. When this player changes clubs, simply change the club in the player setup screen. All the matches that the player has played with previous clubs will still be preserved. Additionally, this player will still show up on statistics reports for the previous clubs even though he/she no longer plays for that club.

Q. What limit is there on the number of matches and players that I can enter into Rugby Statz?

There is no limit on the number of matches or players for a Rugby Statz database other than the size of your hard drive. As a rule, 100 matches will consume around 400kB of hard drive space.

Q. Should I create a new database for every new season?

No. You should keep adding match data to a single database so that you can maintain all records in a single file. You can easily run season reports from the single database by limiting the date range when you run the report.

Q. My club has various junior competitions, grouped by age, and various grades of senior competition. How should I set up my databases?

This is a very common requirement. All games in your senior competition should be entered into a single database. This will allow senior players to easily move up and down grades during the season, if required. Statistics can easily be produced on a per grade basis (if required) by selecting that grade when running the reports. The junior database should be treated the same way as the seniors, that is, having each age group as a different grade. It is probably wise to separate the junior and senior databases simply because players usually do not move back and forth between the two.