DECLARATION

16

DECLARATIONI LWANGA DAVID do declare that the following work is my original copy in which I have compiled all the necessary items. No part of this project has been presented for an academic award in any place. No part of this project should be republished without my permission.

Student Registration No.: ...............................................................Student signature: ..........................................................................Date: ............................................................................................Approved by:Name of the supervisor: ..................................................................Supervisor signature: ......................................................................Date: .............................................................................................

ACKNOWLEDGEMENTThe special thank goes to Mr.John Muniu who has been helpful and supportive throughout my project period. I also appreciate all my friends for their support and encouragement, especially my Dad and Mum and my brother Julius G Lwanga for their support and standing with me through prayers and financially. Without their efforts, the completion of the project would not have been possible.

I highly thank God for giving me the strength to successfully complete this project.

DEDICATION I wish to dedicate this work to my Dad for having faith in me and for been supportive in my life.

ABSTRACTMy Projects title is HOSTEL MANAGEMENT SYSTEM designed for UpperHill Hostels. The main purpose of this project is to introduce a computerized environment to the hostel. The project objectives is to give a system that will be fast to speed up operations, provide a less paper office, give a systematic and efficient way of keeping Hostel records to avoid duplication and to give a secure method of keeping room records to avoid data loss and intentional edit of data.The project will cover Hostel admission, Payment, Expenditure, Room and Allotment parts. This is to ensure that all personal data needed for a student is entered in the system during admission and all payment and allotment record are correctly stored.This project is carried out using Visual Basic as front end and Ms Access as back end.

1. SYSTEM ANALYSIS REPORT2. INTRODUCTIONThe analysis document gives detailed information about the new systems constraints and objectives. It also lists the limitations of the current system.This document lists the methods used to investigate what the user needs.

2.1 INVESTIGATIONThe investigation was conducted using questionnaires, interviews and direct observation. Through these methods the users needs were clearly identified.Questions used during this phase are found in the appendices

2.2 FUNCTIONAL REQUIREMENT SPECIFICATION 2.2.1 INPUT SPECIFICATION

2.2.1.1 HOSTEL ADMISSION Requirements( 70% of Payment + 2 passports) Student First Name, Last name College/University ID/Passport Number Date Of Birth Guardian Year in college Sex

2.2.1.2 PAYMENT Amount paid Admission Number Hostel name Room Number Amount Expected 2.2.1.2 EXPENSES Expense Amount Updater Hostel name Room Number Room type Sex Amount per semester Room capacity

.2.1.2 HOSTEL DETAILS Hostel name Hostel Nick Name Sex Capacity No of Rooms Location2.2.1.2 ROOM ALLOTMENT Hostel name Hostel Nick Name Sex Capacity No of Rooms Location

2.2.2. PROCESSES Calculation of balances Calculation of Total Calculate of Non Allocated vacanciesAssigning Grades

2.2.3 OUTPUT SPECIFICATION Payment Report-Reports showing payments details Room Details Report-Reports on the all rooms in UpperHill hostels Hostel Admission Report-A report that will show admission details. Hostel Report. Show details pertaining each hostel Expenditure Report- A report that will show all expenses incurred. 2.2.4 FILE/DATA STORES 2.2.4.1 HOSTEL ADMISSION Admission Number ID/Passport First Name Last Name Sex Date of Admission Date of birth Guardian College/University Year in College

2.2.4.2 ROOM DETAILS Hostel name Room Number Room type Sex Amount Room Capacity Allocated2.2.4.3 EXPENSES Expense Date Amount Updater Total Expense2.2.4.2 HOSTEL DETAILS Hostel name Hostel Nickname Sex Capacity Room Number Location2.2.4.2 ROOM PAYMENT Receipt Number Full Names Admission Number Room type Room Number Hostel Name Date of payment Amount Expected Amount Paid Balance2.2.4.2 ROOM ALLOTMENT Admission Number ID/ Passport Number First Name Last Name Sex Date of Allotment Hostel Nick Name Room type Room Number Semester Year in Institution2.3 NON-FUNCTIONAL REQUIREMENTSNon-Functional Requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. Access to the system will only be allowed to persons with permission i.e. who are authenticated. All interfaces should be completely understood, so that the system would be able to work with other products or other systems without any restriction. The level of security to avoid damage and loss of information and data. The time that the system takes to react to a given input should be of great consideration. The degree to which the system meets the users requirements and expectations.

2.4 NEW SYSTEMS SCOPE1.8.1 HOSTEL ADMISSIONSThe system will be used in the hostel admission process. If a student is interested with the room, the user must enter the students details in the system; hence the system will be used to assign Hostel admission numbers. 1.8.2 ROOMS PAYMENT AND ALLOTMENTThe system will be used in keeping records of all the amounts paid for the rooms, balances. It will also be used to allot rooms to the students who have already paid hostel fee and have been registered.1.8.3 HOSTEL EXPENDITUREAll hostel expenses are entered in this form. This includes and not limited to water bills, electricity bills, wages and any other expense that occurs during that month. A total expense is calculated.1.8.4 ROOM DETAILSThe system will be used to enter information about each room.1.8.5 HOSTEL DETAILSThe system will be used to input and retrieve information about all New and Old Hostel2.5 OBJECTIVES OF THE NEW SYSTEMThis system is the computerized version of the existing system. Provides easy and quick access over the data Authorization schemes. A system that will be used for assigning Room admission numbers to avoid duplication. A system to keep accurate records for payments made by students for hostels. A systematic way of keeping room details and hostels registration records. A system that will be secure and which can create backups on a regular basis. The user would like a system that is fast while working with it, which will provide an easy way of retrieving and updating records.

2.6 CONSTRAINTS OF THE NEW SYSTEM 2.6.1 Finance The cost of acquiring the required resources brings about a financial constraint since all the hardware and software are to be purchased.

2.6.2 Technical SkillsThe end user need skills to work with the proposed system hence leading to user training

2.6.3 Equipment/ResourcesAll hardware and software to be used must be acquired to enable the development of the new system.

2.7 LIMITATION OF THE CURRENT SYSTEM Errors in records Time consuming Lack of security A lot of space is needed Cumbersome

2.8 USERS OF THE NEW SYSTEM Accountant- For recording payments made by students. Hostels Secretary-Will use the system for adding new hostels, admitting new students and updating all records in the database, maintaining records and creating reports. Director-Create new users as admin and oversee all records of the hostels

RECOMMENDATIONAfter conducting a thorough investigation of UpperHill Hostels current system, it turned out that the new system will solve the limitations of the current system

2. DESIGN PHASEIntroductionWhen designing a system you build a plan for how your project will go through the rest of the stages. E.g. Development and Implementation Stages. This document shows the design of the proposed Hostels Management System for UpperHill Hostels .It shows details of the following: Overall system design Development of a conceptual model Input content, format and validation Naming convention Data validation Output The user interface Charts showing the overall system design Module design and specification Security and backup design Design of a test strategy

2.1 Overall System DesignListed below are the modules for this system.i. Login Module User Login Administrator Log inii. Hostel Admission Moduleiii. Payments Moduleiv. Expenditure Modulev. Room Details Modulevi. Hostels Details Modulevii. Allotment Moduleviii. Report Module

The following table shows a brief description of the Input, Data Type for the input data, Processing and the Output that make up the proposed system based on each module listed above.

ModuleInputData TypeProcessingOutput

Login User

Admin

UsernamePasswordTextTextVerify if username and password are correctAllow access if username and password are correct/Deny access if they are not correct

UsernamePasswordTextTextVerify if Admin username and Admin password are correctAllow access if Admin username and Admin password are correct/Deny access if they are not correct

Hostel AdmissionAdmission NumberID/PassportFirst NameLast NameSexDate of AdmissionDate of birthGuardianCollege/UniversityYear in CollegeTextTextTextTextTextDate/TimeDate/TimeTextTextNumberAdd the new student to the database and assign Admission NumberDetails of the new student

Room DetailsHostel nameRoom NumberRoom typeSexAmountRoom CapacityAllocatedTextTextTextTextCurrencyNumberNumberAdds a new room to the database and automatically assigns room numberDetails of the new hostels and calculates the number of vacancy left.

Expenditure DetailsExpenseDateAmountUpdaterTotal Expense

Text Date/TimeCurrencyTextAmountCalculate Total expenses

Store the data in the expenditure fileDetails of the all expenses.

Room PaymentReceipt NumberFull NamesAdmission NumberRoom typeRoom NumberHostel NameDate of paymentAmount ExpectedAmount PaidBalanceTextTextTextTextTextTextDate/TimeCurrencyCurrencyCurrencyCalculate the balanceStore the data in the payment fileShow the details and calculate the balance of each student

Room allotmentAdmission NumberID/ Passport NumberFirst NameLast NameSexDate of AllotmentHostel Nick NameRoom typeRoom NumberSemesterYear in Institution

TextNumberTextTextTextDateTextTextTextNumberNumberAllots a room and stores the data in the room allotment file.Reports of the rooms allotted.

Hostels DetailsHostel nameHostel NicknameSexCapacityRoom NumberLocationTextTextTextNumberTextTextStore the data in the Hostels details fileHostels details Report

ReportAdmission Number

TextSearch details of the student whose admission number matches the one that the user typedShow reports of all studentsDetails of the student whose admission number matches the one that the user typed

2.2 Development of a conceptual moduleThe proposed system comprises the following entities: Admissions Payments Expenditures Room Details Room allotments Hostel details

2.2.1 Entity Relationship Diagrams (ERD)

StudentAdmission Can be admitted Can be done

One student can be admitted only once Admission can be done to many students

StudentPayment Can make Can be made

Students can make more than one payment Payment can be made by more than one student

StudentsRoom Can be allotted to Can allot One room can be allotted many students Many students can stay one room

HostelExpensesCan have severalCan be

One hostel can have several expenses. Several expenses one hostel

2.2.2 Admission, Payment, Expenditure, Allotment, Room and Hostel attributes2.2.2.1 Admission Table attributes Admission Number ID/Passport First Name Last Name Sex Date of Admission Date of birth Guardian College/University Year in College

2.2.2.2 Payment Table attributes Receipt Number Full Names Admission Number Room type Room Number

2.2.2.3 Room Table attributes Hostel name Room Number Room type Sex Amount Room Capacity Allocated

2.2.2.4 Expenditure Table attributes Expense Date Amount Updater Total Expense2.2.2.5 Hostels Table attributes Hostel name Hostel Nickname Sex Capacity Room Number Location2.2.2.6 Room allotment Table attributes Admission Number ID/ Passport Number First Name Last Name Sex Date of Allotment Hostel Nick Name Room type Room Number Semester Year in Institution2.3 Input Content, Format and Validation The following are tables in the databaseTABLE 2.3.1 ADMISSIONField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

AdmNoTextAdmission Number-8YesNo duplicate

ID/PassportNumberIdentity card/Passport Number-10NoIs Not Null

First nameTextFirst Name-18NoIs Not Null

Last nameTextLast Name-22NoIs Not Null

SexTextSex-25NoIs Not Null

Date of admissionDate/TimeDate of Admission -NoIs Not Null

Date of birthDate/TimeDate of Birth-4NoIs Not Null

GuardianTextParents or Guardian phone number1NoA or BIs Not Null

College/UniversityTextCollege or university

Year in collegeNumberThe year in college of University

TABLE 2.3.2 PAYMENTField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

Receipt NumberTextReceipt Number-8YesIs Not Null

Full NamesTextFirst Name -6No-

Admission NumberTextAdmission Number-6No-

Room typeTextRoom type-6No-

Room NumberTextRoom Number-5NoIs Not Null

Hostel nameTextName of the Hostel-1NoIs not null

Date of paymentDate/TimeDate of Payment-NoIs Not Null

TABLE 2.3.3 EXPENDITUREField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

ExpenseTextExpense Incurred-8YesNo duplicate

DateDate/TimeDate-5-Is Not Null

AmountCurrencyAmount -3--

UpdateTextName of person updated the expense-3--

Total ExpenseIntegerOverall expense-3--

TABLE 2.3.3 ALLOTMENTField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

AdmNoTextAdmission Number-8YesNo duplicate

ID/PassportTextIdentity card/Passport Number-10NoIs Not Null

First nameTextFirst Name-18NoIs Not Null

Last nameTextLast name-

22NoIs Not Null

SexTextSex-25NoIs Not Null

Date of allotmentDate/TimeDate of allotment-NoIs Not Null

Hostel nick nameTextNick name given to a hostel-4NoIs Not Null

Room typeTextRoom type1NoA or BIs Not Null

SemesterSemester

Year in InstitutionNumberYear in Institution

TABLE 2.3.3 ROOM DETAILSField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

Hostel NameTextName of the hostel-8YesNo duplicate

Room NumberTextRoom Number-10NoIs Not Null

Room typeTextType of the room-18NoIs Not Null

SexTextSex-

22NoIs Not Null

AmountCurrencyAmount paid-25NoIs Not Null

Room capacityNumberNo of student s it can hold-NoIs Not Null

AllocatedNumberThe number of students allocated to a room-4NoIs Not Null

TABLE 2.3.3 HOSTEL DETAILSField NameData TypeDescriptionDefault ValueSizePrimary KeyValidation

Hostel NameTextName of the hostel-8YesNo duplicate

Hostel NicknameTextNick name given to a hostel-10NoIs Not Null

SexTextSex-18NoIs Not Null

CapacityNumberNumber of students it can hold-

22NoIs Not Null

Number of RoomsNumberNumber of rooms a hostel can hold-25NoIs Not Null

LocationTextWhere hostel is located-NoIs Not Null

2.4 Naming ConventionAll table names are all written in capital letters and in bold, whereas the field names and the data types start with a capital letter followed by small letters. When a field name has two words joined by an underscore sign, both words start with capital letters. In the primary key column, a YES means that the field is the primary key in the table while a NO means the field is not the primary key.

2.5 Data ValidationData entered in the system must be valid before saving it in the systemThe following table shows data to be entered in the system and its validation rule.

DetailsValidation Rule

Admission NumberMust not be nullNo duplicates

First nameMust not be null

Last NameMust not be null

ContactMust not be null

ExpenseShould not be null

Room typeMust not be null andshould be either Single or Double

StreamMust not be null and should be either A or B

Date of AdmissionMust not be nullAnd should not be later thancurrent date

Fees_paidMust not be null

Date(of payment)Must not be nullAnd should not be later thancurrent date

2.6 OUTPUTThe proposed system will produce the following reports: Payment Report-Reports showing payments details Registration Report-Reports on the Hostel Admissions. Room details Report- A report that will show all information about rooms Hostels Report- This will show inform about the hostels e.g. capacity, name etc Expenditure- This will show information about expenses incurred by the hostel Allotment- Shows the number of free and occupied vacancyEach report must have the Hostel name, name of the report, and date and page number.

2.6.1 Payment ReportThis report will give the user payment details for all students. The details in the report will be: Admission Number, Receipt No, Name, Room type, Room Number, Hostel Name, Date of Payment, Amount Expected, Amount Paid and Balance.The following diagram depicts a sample of the payment reportNb: Balance is got after calculation

Room Payment report UPPER HILL HOSTELS (current date) ROOM PAYMENT REPORT (Page #) LogoAdmission NumberReceipt NoNameRoom typeRoom NumberHostel NameDate of PaymentAmount ExpectedAmount PaidBalance

2.6.2 Admissions ReportThis report will show details of all the students Registered in Hostel. The details to be displayed in the form will be: Admission Number, ID/Passport No, First Name, Last Name, Date of Birth, College, Date of Registration, Sex, Guardian and Year in collegeThe following diagram depicts a sample of the Admission report

Hostel Registration report UPPER HILL HOSTELS (current date) HOSTEL REGISTRATION REPORT (Page #) LogoAdmission NumberID/Passport NoFirst nameLast nameDate of BirthCollegeDate of RegistrationSexGuardianYear in College

2.6.3 Admission Report

2.6.3 Hostel Details ReportThis report shows details about all the Hostels. The details to be displayed in the form will be: Hostel Name, Hostel Nick name, Sex, Capacity, No of rooms and LocationThe following diagram depicts a sample of the Hostel Details report

Hostel Details report UPPER HILL HOSTELS (current date) HOSTEL DETAILS REPORT (Page #) Hostel NameHostel Nick NameSexCapacityNo of RoomsLocation

Logo

2.6.4 Expenditure report2.6.4 Hostel expenditures reportThis report will show details of expense incurred by the Hostel. The details to be displayed in the form will be: Expense,The following diagram depicts a sample of the Expenses report

Hostel Expenditure report UPPER HILL HOSTELS (current date) HOSTEL EXPENDITURE REPORT (Page #)

Logo

UpdaterTotalAmountDateExpense

Overall Total Expense= (Amount)

Prepared by: ___________________

2.6.5 Room Details ReportThis report shows details about the Room. The details to be displayed in the form will be: Hostel Name, Room Number, Room Type, Amount Per Month, Capacity, Sex and Allocated.The following diagram depicts a sample of the Room Details report

Hostel Details report UPPER HILL HOSTELS (current date) HOSTEL DETAILS REPORT (Page #)

Room TypeAmount per MonthCapacitySexAllocatedRoom NumberHostel Name

2.6.2 Room allotment ReportThis report will show Room allotted and by whom. The details to be displayed in the form will be: Admission Number, ID/Passport No, First Name, Last Name, Date of Birth, College, Date of Registration, Sex, Guardian and Year in collegeThe following diagram depicts a sample of the Admission report

Room allotment Report UPPER HILL HOSTELS (current date) HOSTEL REGISTRATION REPORT (Page #)

Logo

Admission NumberLast NameDate of Allotment

ID/Passport NoRoom TypeSex

Semester

First nameHostel Name

Last nameHostel Nick NameYear in College

2.7 The User InterfaceThe system will provide user interfaces that are simple and easy to use 1.7.1 User Sign-In InterfaceThe user will be required to enter a user name and a password of which upon successful login the user will be able to access the system otherwise access will be denied.

Password:Username:OkCancelUser Login

2.7.2 Activities InterfaceThis will be the first interface to appear after the user successfully logs in. The user will select one activity from the list in order to perform any task. The following diagram shows the activities interface

Select an activity Make PaymentPerformanceUpdateReportsCancelAdd New StudentSPRING FIELD GIRLS SECONDARY SCHOOLSelect activity

2.7.3 Admission InterfaceThis interface will appear when the user is admitting a new student.

File Edit Admission Number Surname Other Names Contacts Address Date Form StreamAdd New StudentSaveNewExit AdmissionSPRING FIELD GIRLS SECONDARY SCHOOL

2.7.4 Payment InterfaceThe user will use this interface when recording payments made by the students.

SPRING FIELD GIRLS SECONDARY SCHOOLEnter the following detailsAdmission Number Form Term Amount Paid Total Balance PaymentSaveNewExit PaymentsCalculate

2.7.5 Performance InterfaceThis interface will appear when a user selects the performance activity.

SPRING FIELD GIRLS SECONDARY SCHOOLEnter the following detailsAdmission Number CAT1 Average Form CAT2 Average Stream End Term Average Exam Grade Total Overall Grade Average Enter MarksNewSaveExitPerformance ListMarks

Performance

2.7.6 Update InterfaceThis interface will be used when the user wants to make changes or view students records.

File ExitAdmission Performance Payment Backup Update Admission Records

Exit

Admission Records Adm_No Surname Other_Names Contacts Address DateofAdmission Form Stream

View

Edit

2.8 Chart showing overall system design SPRING FIELD GIRLS SECONDARY SCHOOL STUDENTS INFORMATION MANAGEMENT SYSTEM SYSTEM DESIGN FLOWCHART

NOYESYESYESNONOYESYESNOYESNONOOYESAdmission?Payment?Check all requirementsMeets all requirements?No admissionEnter students detailsVerify if data is validNew Student?Enter students details and amount paidNew student?Admission FilePayment FilePerformance fileAll data is valid?Enter amount paidPerformance?Enter students details and ScoresEnter scoresStopStartCalculationsCalculations

2.8.1 Flowchart key

Rounded rectangle- Shows start / stop

Decision-used where there are two choices to make (Has two options yes or no).

Manual operation-Indicates that there is manual work to be done while using the system.

Manual input-A user must input data manually. For example, key in data from the keyboard

Process-Shows verification and execution/transformation of data in the system

Data store-Shows a storage file for storing/stored data in the system.

Document-in this case it shows a document from the manual operation to show there is no admission.

Data flow -Shows the flow and direction of data in the system .the arrow head shows the destination of the data.

2.8.2 Flowchart Algorithm1. Start2. If activity is admission, then go to step 5.3. If activity is payment, then go to step 12.4. If activity is performance, then go to step 16.5. Check if a student meets all requirements(Manually)6. if student meets all requirements, then go to step 87. If student does not meet all requirements, No admission.8. Enter student details.9. Verify if entered data is valid.10. If data entered is not valid, then go back to step 811. File student details (if student details are valid).12. If payment is for a new student, go to step 14.13. Enter amount paid (if payment is not for a new student), go to step 15.14. Enter student details(if payment is for a new student)15. Calculations(Calculate fee balance)16. File student payments details in the payment file.17. If performance is for a new student, then go to step 19.18. Enter performance details (if performance is not for a new student), go to step 2019. Enter student and performance details (if performance is for a new student).20. Calculations(Calculate total, average and grade)21. file student performance details in the performance file22. Stop

2.9 Module Design and SpecificationModules in the proposed system (Listed in no. 1.1)i. User Sign-in Moduleii. Admission student Moduleiii. Payment Moduleiv. Performance Modulev. Update Modulevi. Report Module

2.9.1 User Sign-in ModuleThis module will allow user to access the proposed system due to security reasons.It will be the first interface after the user opens the proposed system. Pseudo codeUser opens the proposed systemUser types a username and passwordClick ok to sign in, user can click cancel to exit the systemIf username and password does not match the ones stored in the database a message is displayed to show that the username or/and password are incorrect and user should retry.If there is a match in the database, user is allowed access to the proposed system

2.9.2 Admission ModuleThis module will be used to add a new student details in the proposed systems database. The module will have a simple user interface where the user will be required to enter the students Surname, Other Names, Contacts, Address, Date, Form, admission number and the stream which the user must assign. Pseudo codeUser assigns admission number and enters the required data (details) User saves the new records If user violates any validation rule a message is displayed to show the errorIf user clicks new, empty fields are displayed to enter new students detailsUser can navigate through the saved records using the data controlClick exit to close the admission window

2.9.3 Payment ModuleThis module will be used to record a payment done by the student.

Pseudo code*User enters admission number and amount of fee paidUser clicks calculate to calculate the balance. User clicks save to add the new payment into the database

2.9.4 Update ModuleThis module will be used to view and edit student records. This module will also provide the user with an option of backing up data and adding a username.

Pseudo codeUser selects update from the activities windowUser selects what he/she wants to do from the tabsUser can print records inform of a tableExit the module

2.9.5 Report moduleThis module will be used to view reports of all students. There will be three different reports; admission, Payments and performance

Pseudo codeUser selects reports from the activities windows User selects which report to viewA report is displayed on the screen depending on user selectionUser can print the reportExit report module

2.10 Security and Backup Design When a user wants to use the proposed system he/she will be required to log in with a valid username and password, otherwise, access to the system will be denied. This will be for security reasons to shun people with malicious intention from accessing the system.

***The system will provide an option backup to backup data. The backup will be done once in a week, where it will be saved on a compact disk incase the computer fails to function. This type of backup will allow the user to restore back the system as per the last time the backup was done.

2.11 Design of a test strategyi. Logical testingThe system will be tested using the logical operators (And/Or) relating to the data it should accept and store in its database.ii. Functional testingThis type of testing will be done to all modules separately to test if it gives out the expected output/results as per the system design.iii. System testingSystem testing will be done to the system as a whole to test if the proposed system meets users requirements and its objectives. Module compatibility will also be tested in system testing.iv. Recovery testingThis type of testing will test how well and fast the system recovers from crashes, hardware failures or other problems.v. User acceptance testingIn this type of testing the users will be allowed to use the system for sometime to test if the system meets his/her requirements. If the users approve the system then the system will be implemented.

2.12 Requirements of the Design phase Login.Frm Admission.frm Performance.frm Payment.frm Activities.frm Admission.dsr Performance.dsr Payment.dsr

3. CODING AND DEBUGGING 3.1 Login.frmPrivate Sub Form_Load()'set visisbility properties to falseFrmUpdate.AdoConnect.Visible = FalseAdoLogin.Visible = FalseEnd Sub

Private Sub cmdOK_Click()On Error GoTo 41:'Select a username and password that matches the ones in the textboxes from the database

AdoLogin.RecordSource = "SELECT * FROM Login WHERE UserName='" + TxtUserName.Text + "'" AdoLogin.Refresh If (AdoLogin.Recordset.EOF = False) Then If (txtPassword.Text = AdoLogin.Recordset.Fields("Password")) Then MsgBox "Login success", , "Feedback " 'if there is a username and password match Unload Me FrmSelectActivity.Show Else MsgBox "Invalid Password", , "Feedback " 'if there is no password match txtPassword = "" txtPassword.SetFocus End If Else MsgBox "Invalid username", , "Feedback " 'if there is no password match TxtUserName = "" txtPassword = "" TxtUserName.SetFocus End If Exit Sub41: MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error" End Sub

Private Sub cmdCancel_Click()EndEnd Sub

3.2 Admission.frmPrivate Sub CmdSave_Click()On Error GoTo 1'Set text boxes to add data to the fields in the databaseAdoView.Recordset.Fields("Adm_No") = TxtAdmNo.TextAdoView.Recordset.Fields("Surname") = TxtSurname.TextAdoView.Recordset.Fields("Other_Names") = TxtOther.TextAdoView.Recordset.Fields("Contacts") = TxtContacts.TextAdoView.Recordset.Fields("Address") = TxtAddress.TextAdoView.Recordset.Fields("Stream") = CboStream.TextAdoView.Recordset.Fields("Form") = CboForm.TextAdoView.Recordset.Fields("DateofAdmission") = TxtDate.TextAdoView.Recordset.UpdateMsgBox "Record Saved", , "Response"Exit Sub1:MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error"End Sub

Private Sub MnuSave_Click()On Error GoTo 2'Set text boxes to add data to the fields in the databaseAdoView.Recordset.Fields("Adm_No") = TxtAdmNo.TextAdoView.Recordset.Fields("Surname") = TxtSurname.TextAdoView.Recordset.Fields("Other_Names") = TxtOther.TextAdoView.Recordset.Fields("Contacts") = TxtContacts.TextAdoView.Recordset.Fields("Address") = TxtAddress.TextAdoView.Recordset.Fields("Stream") = CboStream.TextAdoView.Recordset.Fields("Form") = CboForm.TextAdoView.Recordset.Fields("DateofAdmission") = TxtDate.TextAdoView.Recordset.UpdateMsgBox "Record Saved", , "Response"Exit Sub2:MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error"End Sub Private Sub CmdNew_Click()On Error GoTo 3:'add a new Record to the recordsetAdoView.Recordset.AddNewTxtAdmNo.SetFocus 'set focus to the Admission Number textboxTxtAdmNo = "SPR000"TxtAddress = "P.o.Box"'Set the default Value of the admission number to SPR000Exit Sub:3:MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error"End Sub

Private Sub MnuNew_Click()On Error GoTo 4:'add a new Record to the recordsetAdoView.Recordset.AddNewTxtAdmNo.SetFocus 'set focus to the Admission Number textboxTxtAdmNo = "SPR000" 'Set the default Value of the admission number to SPR000Exit Sub4:MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error"End SubPrivate Sub MnuDelete_Click()On Error GoTo 5:'Delete a record from the recordsetWith AdoView.Recordset.Delete.MoveNextIf .EOF Then.MovePreviousIf .BOF ThenMsgBox "the record set is empty", , "No records"End IfEnd IfEnd WithExit Sub5:MsgBox "Error No.""" & Err.Number & vbNewLine & Err.Description, vbCritical, "Error"End SubPrivate Sub CmdExit_Click()'Hide admission FormUnload Me'Show the select activiivy FormFrmSelectActivity.ShowEnd SubPrivate Sub MnuExit_Click()'Hide admission FormMe.Hide'Show the select activiivy FormFrmSelectActivity.ShowEnd Sub

Private Sub CmdExt_Click()'Hide admission form Me.HideFrmSelectActivity.ShowEnd Sub

3.3 Payment.frm

Private Sub CmdCalculate_Click()On Error GoTo 31:'declaring variablesDim total As IntegerDim balance As IntegerDim paid As IntegerDim message As StringDim Form1 As StringDim term As StringDim bal1, bal2, bal3, totalFee As Currency

'variable initializationForm1 = CboForm.Textterm = CboTerm.Textpaid = TxtFeePaid.TextTxtBal1 = balance

'CalculationsIf Form1 = "One" Or Form1 = "Two" Then 'And term = "1" Then If term = "1" Thentotal = 12500totalFee = total + bal3balance = total - paidbal1 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal1.Text = bal1ElseIf term = "2" Thenbal1 = TxtBal.Texttotal = 13000totalFee = total + bal1balance = total - paidbal2 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal2.Text = bal2ElseIf term = "3" Thenbal2 = TxtBal2.Texttotal = 11000totalFee = total + bal2balance = total - paidbal3 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal3.Text = bal3TxtBal2.Text = 0 ElseMsgBox "Term or Form not valid"End IfEnd IfEnd IfEnd If'End IfIf Form1 = "Three" Or Form1 = "Four" And term = "1" Then If term = "1" Thentotal = 13500totalFee = total + bal3balance = total - paidbal1 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal1.Text = bal1ElseIf term = "2" Thenbal2 = TxtBal1.Texttotal = 14000totalFee = total + bal1balance = total - paidbal2 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal2.Text = bal2

ElseIf term = "3" Thenbal2 = TxtBal1.Texttotal = 12000totalFee = total + bal2balance = total - paidbal3 = totalFee - paidTxtTotal.Text = totalTxtBal.Text = balanceTxtBal3.Text = bal3TxtBal2.Text = 0 ElseMsgBox "Term or Form not valid"

End IfEnd IfEnd IfEnd IfExit Sub31:MsgBox "Error #" & Err.Number & vbNewLine & Err.Description, vbCritical, "error"End Sub

Private Sub CmdExit_Click()'hide formFrmPayment.HideFrmSelectActivity.Show

End SubPrivate Sub CmdNew_Click()On Error GoTo 32:'add new recordAdoPayment.Recordset.AddNewTxtAdmNo.SetFocusTxtAdmNo = "SPR000"TxtBal1.Text = 0TxtBal2.Text = 0TxtBal3.Text = 0Exit Sub32:MsgBox "Error #" & Err.Number & vbNewLine & Err.Description, vbCritical, "error"End Sub

Private Sub CmdSave_Click()On Error GoTo 33:'Save New recordAdoPayment.Recordset.Fields("Adm_No") = TxtAdmNo.TextAdoPayment.Recordset.Fields("Fees_Paid") = TxtFeePaid.TextAdoPayment.Recordset.Fields("Form") = CboForm.TextAdoPayment.Recordset.Fields("Date") = TxtDate.TextAdoPayment.Recordset.Fields("Total") = TxtTotal.TextAdoPayment.Recordset.Fields("Balance") = TxtBal.TextAdoPayment.Recordset.Fields("BalTerm1") = TxtBal1.TextAdoPayment.Recordset.Fields("BalTerm2") = TxtBal2.TextAdoPayment.Recordset.Fields("BalTerm3") = TxtBal3.TextAdoPayment.Recordset.UpdateMsgBox "Record Saved", , "Response" Exit Sub33:MsgBox "Error #" & Err.Number & vbNewLine & Err.Description, vbCritical, "error"End Sub

Private Sub MnuSave_Click()AdoPayment.Recordset.Fields("Adm_No") = TxtAdmNo.TextAdoPayment.Recordset.Fields("Fees_Paid") = TxtFeePaid.TextAdoPayment.Recordset.Fields("Form") = CboForm.TextAdoPayment.Recordset.Fields("Date") = TxtDate.TextAdoPayment.Recordset.Fields("Total") = TxtTotal.TextAdoPayment.Recordset.Fields("Balance") = TxtBal.TextAdoPayment.Recordset.Update

End Sub

3.4 Performance.frmOption Explicit 'general declaration'Dim term As Integer'Dim CAT1 As String'Dim CAT2 As String'Dim Endterm As Integer

Private Sub CmdMarks_Click()On Error GoTo 123:'declaring variablesDim Marks() As IntegerDim Counter As IntegerDim Grade As StringDim Average As StringDim message As StringDim total, TotalAvg As IntegerDim Form1 As StringDim exam As StringDim term As IntegerDim CAT1 As IntegerDim CAT2 As IntegerDim Endterm As IntegerDim OverallGrade As String

'initializationtotal = 0Form1 = CboForm.Text

'calculationsIf Form1 = "One" Or Form1 = "Two" Then ReDim Marks(11)For Counter = 1 To 11 Marks(Counter) = InputBox("Enter Marks", "Marks Prompt")

ListMarks.AddItem Marks(Counter) total = total + Marks(Counter) TxtTotal.Text = total Average = total / Counter TxtAverage.Text = Average Next 'Assigning gradesIf Average