Once the method was chosen, the design became apparent.
The form basically offers two options for the user. One, to view previous results and two, to enter results online. Initially, the user has to choose on the year of competition, then the week and finally the teams to play for that week. From here the option varies. The user can either view the results, if the year selected is in the past or else can update the results for present and future games. This is done by virtually hiding all the controls present in the form until the user clicks on the appropriate buttons which are ‘View’ and ‘Update’ (the names are self-explanatory). This is done by marking a tag to all these controls and setting their visible property to ‘false’. A sample piece of code is shown below.
Once these are decided, the user can select the ‘GO’ button, to view the result input boxes filled with players’ names adjacent to them. Once the user fills and clicks on ‘Save’, th e data gets stored in appropriate tables. The query used to update these values is given below:
The creation of the financial report detailing the players who are members for current fiscal and those who are not basically depends on the data available in the two tables namely, ‘Members’ and ‘Players’. These tables contain details regarding the players, their member ids and their membership details. The report is created using the Report Wizard of MS Access which lists out the fields that need to be presented in the report in addition to the variables based on which the report has to be ordered.
The report is generated by analysing the value of the ‘Members’ table field column, pCurrent which mentions whether the player is member or not. If the value for a member id is ‘Y’, the player is a member and if ‘N’, the player has to renew is membership. Based on the member ID and Player Id relationship, the player details are