Homework answers / question archive / Project Guidelines and Past Exams Database Project Guidelines As part of the FETAC Level 5 Database Methods module (awarded by QQI) you are required to complete a database project

Project Guidelines and Past Exams Database Project Guidelines As part of the FETAC Level 5 Database Methods module (awarded by QQI) you are required to complete a database project

Computer Science

Share With

---

Project Guidelines and Past Exams

Database Project Guidelines

As part of the FETAC Level 5 Database Methods module (awarded by QQI) you are required to complete a database project. The project tests if you can apply what you have learned about databases to a fictitious problem and then design and create a database to solve the problem. The problem may be in a business context, such as the need to computerise the stock control system of a small business, or it may be in relation to an interest or hobby, such as creating a database to manage the administration of membership in a local club.

 

The Database Project should be completed in three distinct phases:

Phase 1: Design 

Phase 2: Implementation 

Phase 3: Proposed Modifications 

 

The project must be completed in this order. You must design your database on paper before you set it up in Access. 

 

Phase 1: Design 

1. Describe the aims of your project
2. Specify Table structure
3. Design a Data Capture Form
4. Specify Queries and Reports

 

Describe the Aims of Your Project

1. Provide some background information to set the scene for your project.

 

Example

Riverstown Karate Club was established in 1998. Since the club was formed, all information about the club and its members has been kept in a paper-based filing system. This is very cumbersome and takes up valuable space. Mistakes have been made from time to time when locating and retrieving information. Not only does it take time to find a member’s application form or progress sheet, but it is difficult and time-consuming to keep records up to date. The aim of this project is to create a database to store the information relevant to the running of the club. The database will reduce the amount of time required for administration work and make it easier for the instructors to run the club.

 

2. Identify problems that exist in the system you have decided to computerise using a database. For each problem that you identify, describe in detail how the database will solve the problem.

        

Example

Problem

Gradings occur twice yearly. To prepare for the gradings, the instructors draw up lists of members in each Belt Ranking Category, e.g. black belt, brown belt, etc. This is very timeconsuming and sometimes members are unintentionally omitted from the lists. Producing lists of members in alphabetical order is very difficult because the lists are created using Microsoft Word. If new members join the club prior to a grading, these have to be added to the list of members to be graded by inserting their names in separate word processing documents.

 

Solution

In the Database system, a Report will be created to group members according to their current belt ranking. Within each group, members will be sorted in alphabetical order of surname. A Report function will count the number of members in each belt ranking category so the instructors know exactly how many students to expect at each grading. If new members join prior to the grading, they will be picked up automatically by the Report and listed in alphabetical order once they have been entered in the Database.

 

Specify Table Structure

1. Identify where the data that will be stored in your database exists in the current system.

 

Example

The data relating to members is taken from the club’s paper files, i.e. the old system of keeping records. Information on black-belt club members is taken directly from instructors, as is the data on all of the club members due to be graded for their black belt.

 

2. Specify fields included in the Table. For each field, indicate the data type, field size in bytes and give an example of data that will be stored in the field. Identify which field is the Primary Key.

 

Example: Membership Table

Field Name	Data Type	Field Size	Example
Membership No	Number	Integer (2)	298
First Name	Text	25	Richard
Surname	Text	25	Butler
Gender	Text	7	Male
Address1	Text	35	1 Riverstown Wood
Address2	Text	25	Clonmel
Address3	Text	25	Co. Tipperary
Age	Number	Byte (1)	16
Current Belt	Text	10	Yellow
Membership Fee	Currency	8	€360
Date of Last Fee Renewal	Date/Time	8	15/05/2011
Paid	Yes/No	1	Yes

Table 11.1

 

Membership No is the Primary Key field.

 

Design a Data Capture Form

A Data Capture Form is a printed form used to collect data before it is entered in a database.

It should be designed to capture all of the input data. We have all filled in Data Capture Forms at one time or another: club membership forms, an application form for a bank account or the CAO form. It is a good idea to look at how Data Capture Forms are designed in practice before you create your own. A well-designed Data Capture Form will:

• be easy to complete
• contain instructions on how to complete the form
• indicate to whom the form is to be returned or where the form is to be sent when it is completed
• be well laid out on the page using appropriate fonts, colours, tick boxes and lines (for writing names and addresses).

 

The Data Capture Form must include all of the fields that you have specified for your Table. A sample Data Capture Form is shown below.

 

        

 

 

 

 

Specify Queries and Reports

1. Specify Query structure

The database project must include two or more appropriate queries. At least one Query must have an and/or condition. The queries should solve problems identified earlier in the project. Each Query should be specified using the following headings:

• Query Name
• Purpose of Query
• Table(s) linked to • Fields in Query
• Query conditions

 

Example

Query Name: Members eligible for Black Belt grading.

 

Purpose of Query: To find all members who currently hold a Brown Belt and who have paid their membership fee.

 

Tables linked to: Membership

 

Fields in Query: Membership No, First Name, Surname, Age, Current Belt, Paid

 

Query Conditions

Field Name	Current Belt	Paid
Criteria	“Brown”	“Yes”

Table 11.2

 

2. Specify Report Structure

 

The project must include at least four appropriate Reports. Each Report must be sorted or grouped or both. (A mail merge can be used as a Report.) Labels must be produced by one of the Reports. Report functions should be used where appropriate. The Reports should solve problems identified earlier in the project. Each Report should be specified using the following headings: • Report Title

• Purpose of Report
• Table or Query linked to
• Fields in Report
• Sort and Grouping 
• Report Functions 

 

Example

Report Title: Current Members’ Belt Rankings

 

Purpose of Report: This Report will display all members’ names and their belt rankings. It will allow instructors to determine which members are in a specific belt ranking category. The Report will be grouped by Current Belt.

 

Linked to: Membership Table

 

Fields in Report: Current Belt, Membership No, First Name, Surname

 

Sort and Grouping: The Report will be grouped by Current Belt and sorted in ascending alphabetical order of Surname within each group.

 

Report Functions: The function =count([Membership No]) will be included in the Current Belt Footer to calculate the number of members in each belt ranking category.

 

Phase 2 – Implementation 

1. Data accurately inputted
2. Database used to sort, query and organise data effectively
3. Reports with headings and sum and average calculation accurately produced
4. Labels with multiple fields accurately produced
5. Database Queries and Reports saved and printed

 

Data accurately inputted

Your Table should include a minimum of 25 records and 5 fields and must have at least one numeric field. Try to include as many different field data types (Text, Number, Date/Time, Currency, Yes/No, Autonumber, Memo) as possible in the Table – you will learn more from your project as a result. The data should be inputted using a Form that is linked to the Table. Marks will be deducted for spelling errors, as a single data entry error can affect multiple Queries and Reports. When you have finished inputting the data, proofread it and correct any errors.

 

Database used to sort, query and organise data effectively

Sorting should be implemented using Reports. Reports must be either sorted or grouped or both. In the case of the Riverstown Karate Club database, a Report displaying members in ascending alphabetical order of Surname could be created. A Grouped Report could be created, splitting members into male and female with a function to calculate the total number of male and female members.

 

Reports with headings and sum and average calculation accurately produced

The overall formatting of the Reports should be attractive and should be consistent across all Reports. Data should be aligned under field headings in each Report. Headings should be spaced evenly across the page. Appropriate functions, i.e. Sum, Avg, Count, Max or Min must be used in either the Report Header, Report Footer or the Group Footer. Calculated fields may also be used, where appropriate. Check the result returned by each function by doing the calculations manually.

        

 

Labels with multiple fields accurately produced

In most cases the Label Wizard is used to create name and address labels. It can also be used to produce labels for other purposes, such as price tags and product identification labels or membership cards. Whatever purpose your labels serve, they will be stored in a Report linked to either a Table or a Query. If you create name and address labels, these could be used in conjunction with a mail merge letter created in Word.

 

Database Queries and Reports saved and printed

When printing Queries and Reports, select an appropriate page orientation for each printout. If there are a lot of fields in a particular Query or Report, set the page orientation to Landscape. Reduce paper wastage by checking your queries and reports in print preview and making necessary adjustments before printing.

 

Phase 3 – Proposed Modifications 

 

1. List the aspects of your project that you are particularly pleased with.
2. Suggest at least 3 ways in which your database could be improved if you had more time. Students often notice limitations in their database design while they are working on a project. These should be noted and used as potential modifications. An in-depth description of each modification should be produced. Modifications should be illustrated using examples and diagrams where appropriate.

 

Example

Given more time, there are modifications that would have been quite relevant and useful to include in my project. One such modification relates to the Query that finds club members who are under 18. A point to note regarding this Query is that a member’s age is not constant. As time passes members get older, but this is not reflected in the database because their ages are recorded as fixed numbers. So, for example, running the under 18s Query today may find 25 members. Running this Query exactly one year from now should find less than 25 members because some members will no longer be under 18. 

 

With the current database design, the Under 18s Query will always find the same number of members unless their ages are updated each year. Because of the way I set up my Table, the under 18s Query will become more and more inaccurate as time progresses unless each member’s age is adjusted on their birthday. With more and more members joining the club, this method is guaranteed to lead to errors. Given that the main purpose of the database is to reduce the administration work of instructors, this design flaw would be unacceptable in a real-life database. 

 

To solve this problem, I would first need a Date of Birth field in the Membership Table. I would then have to, in some way, calculate a member’s age by subtracting their date of birth from today’s date. In this way their age would always be up to date because it would advance with each passing day. This calculation could then be incorporated in the Under 18s Query so that it always finds only those members who are under 18 on a particular date. Possible Database Project Topics

 

1. Club Membership

Create a database to store details of members in a local club. Create queries to find members who qualify for competitions – under 12s, under 15s, under 18s, etc. Create a mail merge to inform members of club events. Use the Label Wizard to create membership cards. Create reports detailing competition lists and competition results.

 

2. Doctor’s Surgery

Store details of patients attending a doctor’s surgery in a database. Create queries to identify private patients and those on medical cards. Use reports to calculate the total receipts over a given time period. Create a mail merge to inform patients of upcoming appointments and to create reminders for those whose bill is overdue.

 

3. Technical Support

Create a database to store details of PCs repaired by Technical Support. Create Queries to analyse the different problems that occurred and who fixed them. Create a Report to display the number of PCs fixed per week and the average cost of fixing a PC. Create a Report that shows which brand of PC gives the most problems.

 

4. Personal Music Collection

Set up a database to store details of your personal music collection. Create parameter queries to find tracks by artist, category or title. Create a report that groups tracks by category and that calculates the total value of the collection.

 

5. Stock Control

Create a database to store details of stock in a shop or small company. Create queries to find products with low stock levels and products past their sell-by dates. Create reports detailing stock movements, the total value of stock by product and the average stock level.

 

6. Dating Agency

Set up a database to store details of a dating agency’s clients. Record clients’ hobbies and interests and then create queries to match up clients. Use the Label Wizard to create a membership card. Create a mail merge to inform clients of upcoming dates. Analyse weekly and monthly receipts using a Report.

 

7. Car Dealership

Store details of cars for sale in a database. Create a Parameter Query that allows a customer to specify their preferences (model, engine size, colour) and that finds records matching their requirements. Create a Report detailing cars for sale grouped by manufacturer. Create labels that display the registration number, model and colour.

 

For more ideas, have a look through the examples and database assignments in Step by Step Databases. The above are only suggestions. The list of possible database projects is endless. What works best is if you can do your database project on a topic that interests you, e.g. a hobby or an area that you have worked in before.

 

FETAC Level 5 Database Methods

Sample Exam 1

Michael O’Brien runs a retail outlet in Nenagh, Co. Tipperary. He specialises in a broad range of adhesive and sealing compounds. Recently he has started to record details of the various products that he stocks. Michael wishes to set up a database to record these details and to enable him to retrieve information easily from the data stored.

 

Task 1

 

1.1 Create a database named Stock Control. o Create a Table named Current Stock to store the data extracted from the records of Michael O’Brien (refer to Table 11.3).

Rec No	Product	Agent	Qty (kg)	Price	Location	Life (wks)
3201	Impact Adhesive	Doyle Bros	5.0	€56.45	Stores	14
3202	Impact Adhesive	Doyle Bros	2.5	€28.50	Shop	12
4215	Sealing Compound	JJ Williams	4.5	€24.80	Stores	28
5247	Roof Sealer	Geo Ryan	5.5	€56.50	Stores	24
5248	Roof Sealer	Geo Ryan	2.5	€28.00	Shop	20
6480	General Adhesive	Geo Ryan	10.0	€120.00	Warehouse	13
6481	General Adhesive	Geo Ryan	5.0	€65.00	Stores	10
6482	General Adhesive	Geo Ryan	2.5	€38.50	Shop	8
7246	Jointing Cement	JJ Williams	25.0	€85.00	Warehouse	6
7247	Jointing Cement	JJ Williams	12.5	€50.00	Stores	5
7248	Jointing Cement	JJ Williams	6.0	€27.50	Stores	4

Table 11.3

 

• Set up the Rec No field as the primary key.
• Set up a validation rule which ensures that values entered in the Life (wks) field are restricted to the range 4–104 inclusive. If the data entry operator attempts to enter a number outside of this range, the error message ‘Life (weeks) must be in the range 4 to 104 inclusive’ should be displayed.

 

1.2 Complete the Database Structure Form provided to show field names, data types and field sizes (refer to Table 11.6 on p. 13).

        

Task 2

 

2.1 Design and create a Form to allow the data entry operator to enter the data shown in Table 11.3. The format of the Form should be as follows:

 

• Insert the title Stock Registration centrally on the Form.
• Display two fields on each line (except the last line).
• Place a label or title beside each field.
• Edit the Rec No label so that it reads Record Number.
• Adjust the width of text box controls to accommodate the data.
• Set the alignment of the Rec No, Qty (kg), Price and Life (wks) text box controls to center.
• Create a combo box for the Product field. Each product should appear once in the combo box in alphabetical order (refer to Table 11.3).
• Create a list box for the Location field. Each location should appear once in the list box in alphabetical order (refer to Table 11.3).
• Line up the label and text box controls both horizontally and vertically.
• Set up the tab order of the form using the order in Table 11.4.

 

	Field Name
1	Rec No
2	Product
3	Agent
4	Qty (kg)
5	Price
6	Location
7	Life (wks)

                                  Table 11.4

 

Save the Form as Stock Registration.

 

Print the Stock Registration Form (either now or later) or call the specialist teacher at the end of the examination to award marks to your Form.

 

2.2 Input the data shown in Table 11.3 using the Stock Registration Form.

 

Task 3

 

Create Queries for each set of criteria listed below. N.B. Print each Query as you complete it.

 

3.1 Select and Print all the records for products where the agent is Doyle Bros.

• Sort the Query in ascending order of Price.
• Save the Query as Doyle Bros.

        

3.2 Select and Print all the records for Adhesive products. Use a wild card to select the required records.

• Sort the Query in ascending order of Location.
• Save the Query as Adhesive Products.

 

3.3 Select and Print all records that are located in the Stores and where the Qty is less than

12.

• Sort the Query in descending order of Qty (kg).
• Save the Query as Stock below 12 in Stores.

 

3.4 Select and Print all the records for products where the Agent is Geo Ryan, where the Price is between €25 and €90 inclusive, and the Life (wks) is greater than 12.

• Sort the Query in ascending order of Location.
• Save the Query as Geo Ryan.

 

3.5 Create a parameter query that can find records of stock in each of the three locations.

The query should display the message ‘Enter stock location’ when it is run.

• Sort the Query in descending order of Agent.
• Save the Query as Stock by Location.

 

3.6 Create a Totals Query that calculates the total quantity of stock in each location and the total value of stock in each location. Save this Query as Stock levels.

 

Task 4

 

4.1 Add a new field to the Current Stock Table as follows: Field Name – Toxic

Data Type –Yes/No 

 

Add the details of the Toxic field to the Database Structure Form (Table 11.6 on p. 13).

 

4.2 Add the Toxic field to the Stock Registration Form and enter data as follows:

All the Adhesive products are toxic.

All other products are not toxic.

 

4.3 Delete the record with Rec No 7247.

 

4.4 Edit the Product combo box, then input the records displayed in Table 11.5 using the Stock Registration Form.

 

Rec No	Product	Agent	Qty (kg)	Price	Location	Life (wks)	Toxic
8324	Quick Adhesive	Doyle Bros	0.5	€6.40	Shop	11	Yes
8325	Bonding Cement	JJ Williams	3.5	€18.60	Stores	9	No

       Table 11.5                                                          

       Task 5                                                                                                                      

 

5.1 Generate a Report from the Current Stock Table including all fields. Sort the Report with the Product field in ascending order (primary sort) and the Life (wks) field in descending order (secondary sort). The Report title is Current Stock List. Print the Report (in landscape orientation) either now or after the exam has finished. Ensure that data is aligned under each heading and that each text box and label is wide enough to display all data.

 

5.2 Generate a Report from the Current Stock Table, to include all of the following:

 

• Show all fields, except Agent and Life (wks).
• Sort the Report in descending order on the Price field.
• Display the title List of Products centrally over the Report.
• Display the appropriate field heading centrally over each column of data.
• Use a function to display the average for the Qty (kg) field at the bottom of the Report. Insert a label with the text Average Quantity beside the function. Format the average quantity to 1 decimal place.

 

Save this Report as List of Products. Print the Report (in portrait orientation) either now or after the exam has finished.

 

Task 6

        

6.1 Produce a set of labels for all products except for roof sealer and sealing compound. The labels should have the following format:

 

• Layout as shown below.
• Have more than one label across the page.
• Sorted in ascending order of Product.
• Agent field in bold print.

 

 

Save these labels as Stock Control Labels.

 

6.2 Print the Stock Control Labels either now or after the exam has finished.

        

Task 7

 

Generate a report from the Current Stock Table, to include all of the following:

 

• Show all fields.
• Group the report by the Location field.
• Sort the records in each Location in descending order of Price.
• Display the title Products by Location centrally over the report.
• Display the appropriate field heading centrally over each column of data.
• Use a function to calculate the total value of products in each location. Display the result of the function in euro format with two decimal places. Insert a label with the text Stock Value beside the function.
• Calculate the average Life (wks) for products in each location, using an appropriate function. Display the result of the function in Fixed format with one decimal place. Insert a label with the text Average Life in weeks beside the function. Position this function below the stock value function.
• Use a function to calculate the total quantity of stock for all products displayed in the Report. Display the result of the function in Fixed format with one decimal place. Insert a label with the text Current Stock Level beside the function.

 

Save this report as Products by Location. Print the report (in landscape orientation) either now or after the exam has finished.

 

 

DATABASE STRUCTURE FORM

 

Field Name	Data Type	Field Size

Table 11.6

 

FETAC Level 5 Database Methods

Sample Exam 2

Paddy Watts is a bookmaker’s chain with outlets in most towns in Ireland. At the Head Office in Galway, a database is required to keep track of bets placed in its various outlets. For this purpose, copies of all dockets are sent electronically to head office. Details are then inserted into the database.

 

Task 1

 

1.1 Create a database named Paddy Watts Betting.

• Create a Table named Betting Details to store the data displayed in Table 11.7.

 

Docket No	Branch	Received Date	Stake	Payout	Type of Bet
101001	Harbour Road, Arklow	06/08/2015	€5.00	€105.00	Treble
101020	Arklow Road, Wicklow	09/08/2015	€100.00	€150.00	Single
101067	Shop Street, Galway	07/08/2015	€20.00	€75.00	Double
101102	Main Street, Arklow	06/08/2015	€40.00	€120.00	Single
101143	Shop Street, Galway	08/08/2015	€200.00	€300.00	Single
101147	Shop Street, Galway	08/08/2015	€500.00	€1,500.00	Single
101154	Bridge Street, Waterford	10/08/2015	€15.00	€195.00	Yankee
101211	Harbour Road, Arklow	11/08/2015	€50.00	€3,000.00	Yankee
101244	Shop Street, Galway	13/08/2015	€50.00	€400.00	Double
101261	Main Street, Arklow	13/08/2015	€10.00	€90.00	Single

Table 11.7

 

• Set up the Docket No field as the primary key.
• Set up a validation rule which ensures that values entered in the Payout field are greater than or equal to the values entered in the Stake field. If the data entry operator attempts to enter a number that breaks the validation rule, the error message ‘Payout must be greater than or equal to the stake’ should be displayed.

 

1.2 Complete the Database Structure Form provided to show field names, data types and field sizes (refer to Table 11.11 on p. 18).

 

Task 2

 

2.1 Design and create a Form to allow the operator to enter the data shown in Table 11.7 in the Betting Details Table.  

• Insert the title Posting Details centrally on the Form. o Display two fields on each line. o Place a label or title beside each field. o Adjust the width of text box controls to accommodate the data. o Set the alignment of the Branch text box control to left. Set the alignment of all other text box controls to center.
• Create a combo box for the Type of Bet field. Each bet type should appear once in the combo box in alphabetical order (refer to Table 11.7).
• Line up the label and text box controls both horizontally and vertically. o Set up the tab order of the form using the order displayed in Table 11.8.

	Field Name
1	Docket No
2	Branch
3	Received
4	Stake
5	Payout
6	Type of Bet

 

                                  Table 11.8

 

Save the Form as Posting Details.

 

Print the Posting Details Form (either now or later) or call the specialist teacher at the end of the examination to award marks to your Form.

 

2.2 Input the data shown in Table 11.7 using the Posting Details Form.

 

Task 3

        

Create queries for each set of criteria listed below. N.B. Print each Query as you complete it.

 

3.1 Select and print all records for bets at the Harbour Road, Arklow branch.

• Sort the Query in descending order of Payout.
• Save the Query as Harbour Road Arklow.

 

3.2 Select and print all records for bets placed in either of the Arklow Branches (use a wild card).

• Sort the Query in descending order of Payout.
• Save the Query as Arklow bets.

 

3.3 Select and print all records for bets at the Shop Street, Galway branch where the Stake was greater than €50.00.

• Sort the Query in descending order of Stake. o Save the Query as Galway bets above €50.

 

1. 4. Select and print all records for bets at the Galway or Wicklow Branches, where the

Payout was between €100.00 and €1,000.00 inclusive, and where the Type of Bet was Single. o Sort the Query in descending order of Payout. o Save the Query as Single bets in Galway and Wicklow.              

• 5. Create a parameter Query that can find records relating to any type of bet. The query should display the message ‘Enter type of bet’ when it is run.
• Sort the Query in descending order of Payout.
• Save the Query as Records by type of bet.

 

3.6 Create a Totals Query that calculates the total payout by branch. Save this Query as Payout by Branch.

 

Task 4

 

4.1 Add a new field to the Betting Details Table as follows:

                  Field Name – Win

                  Data Type – Yes/No

 

Add the details of the Win field to the Database Structure Form (Table 11.11 on page 18).

 

4.2 Add the Win field to the Posting Details Form and enter the data shown in Table 11.9.

 

Docket No	Win
101001	Yes
101020	Yes
101067	No
101102	No
101143	No
101147	No
101154	No
101211	Yes
101244	Yes
101261	No

Table 11.9

 

4.3. Input the records displayed in Table 11.10 using the Posting Details Form.

 

Docket No	Branch	Received Date	Stake	Payout	Type of Bet	Win
101265	Bridge Street, Waterford	15/08/2015	€25.00	€40.00	Single	Yes
101272	Arklow Road, Wicklow	18/08/2015	€75.00	€600.00	Double	No

Table 11.10

        

Task 5

        

5.1 Generate a Report from the Betting Details Table to include all of the following:

 

• Show all fields except Type of Bet.
• Sort in ascending order on the Branch field (primary sort).
• Sort in descending order on the Stake field (secondary sort).
• Display the title Summary of August Bets centrally over the data.
• Align columns under column headings and evenly space across the page.
• Display a grand total for the Payout field, in currency format with no decimals, at the end of the Report. Display the text Total Payout beside the grand total.

 

Save this report as Summary of August Bets. Print the Report (in portrait orientation) either now or after the exam has finished.

 

5.2 Generate a Report from the Betting Details Table, to include all of the following:

 

• Show all fields, except Docket No and Received Date.
• Sort in ascending order on the Branch field (primary sort).
• Sort in descending order on the Payout field (secondary sort).
• Display the title Betting Details by Branch centrally over the Report.
• Display the appropriate field heading centrally over each column of data.
• Use a function to calculate the average for the Payout field at the bottom of the Report. Insert a label with the text Average Payout beside the function. Display the average payout in currency format with two decimal places.

 

Save this Report as Betting Details by Branch. Print the Report (in portrait orientation) either now or after the exam has finished.

 

Task 6

 

Produce a set of mailing labels for all dockets, except those from the Waterford branch. The mailing labels should have the following format:

 

• Layout as shown below.
• Have more than one label across the sheet.
• Branch field in bold print.
• Print in ascending order by Branch.

                      

          BRANCH                                                                               

 

Save these labels as Betting Labels.

        

Task 7

 

Generate a report from the Betting Details Table, to include all of the following:

 

• Show all fields.
• Group the report by the Type of Bet field.
• Sort the records for each Type of Bet in descending order of Payout.
• Display the title Analysis of Betting Results centrally over the report.
• Display the appropriate field heading centrally over each column of data.
• Use a function to calculate the average payout for each type of bet. Insert a label with the text Average Payout beside the function. Display the average payout in currency format with two decimal places.
• Use a function to calculate the total payout for each type of bet. Insert a label with the text Total Payout beside the function. Display the total payout in currency format with no decimals.
• Use a function to calculate the total payout for all bets displayed in the Report. Insert a label with the text Overall Payout beside the function. Display the total payout in currency format with no decimals.

 

Save this report as Analysis of Betting Results. Print the report (in landscape orientation) either now or after the exam has finished.

 

 

DATABASE STRUCTURE FORM

 

Field Name	Data Type	Field Size

Table 11.11