Policy management system project report.pdf

1
AN
PROJECT REPORT
ON
POLICY MANAGEMENT SYSTEM PROJECT
BY
KAMAL ACHARYA
(Tribhuvan University)
Date: 2023/12/10

2
1. INTRODUCTION
1.1 Overview of the Project
The project entitled as “Policy Management System” is developed in a manner to help
all the Policy Agency Members. It is developed using Visual Basic 6.0 as Front-End and MS
Access as the Back-End tool.
The system is designed in such a way that it accepts and stores the input data, process
and produce output under the direction of a detailed step by step stored programmed
instruction. This system includes Client Dairy, Client Details, Add new Client, Policy Details
and Payment Details information’s and gives details based on the policy Number of the client.
This system is necessary for Storing Information, assessing Workload and hence their
efficiency. The System provides the adequate information to the concern for its smooth run.
1.2 About Existing System
MANUAL SYSTEM:
This system involves manual labours, which may lead to problems. It is very
tedious to handle large volume of data and requires more time to handle the information,
which results in slow processing.
Thus the computerization will make it very easy and accurate at all the
processing stages. Report preparation requires more time so by computerizing, it will be
very easy for the management. So the existing system is to be changed and put for
computerization.
2.1.1 DRAWBACKS OF THE EXISTING SYSTEM
1. Tedious to handle large volume of data.
2. Time consumption.
3. Maintaining the manual registers is cumbersome.
4. Decision making is very slow.

3
2. SYSTEM ANALYSIS
2.1 Proposed System
The Proposed System has been designed using Visual Basic as front-end and
MS-Access as back-end. The proposed system is a computerized on with GUI interface. It takes
care of the process under an easy environment to work with.
Proposed System has the following facilities:
The new system is under-friendly.
 The systems provide all possible options to new entry, editing, updating and
searching the Policy and Client.
 The system have the search options in many ways, it is very user friendly.
 The system is highly portable.
 The system provides very good database Management System.

4
3. SYSTEM REQUIREMENT SPECIFICATION
3.1 Hardware Specification
Processor : Pentium IV 2.4GHz
RAM : 512 MB DDR 2
Hard Disk : 80 GB
Floppy disk : 1.44MB
Key Board : United states 101
Monitor : 15’’ Color Monitor
2.3.2 Software Specification
Front-End : Visual Basic 6.0
Back-End : MS Access
Operation System : Windows XP

5
Microsoft Visual Basic 6.0
Microsoft Visual Basic 6.0 is the newest version of the popular
programming language . Version 6.0 of V.B specifically designed to the utilize the internet.
You can develop robust stand alone application, games ,and utilities in less time then it
take in other language .You can also use ActiveX technology to create internet enabled
applications that are limited only by your imagination. This software works under Windows
95, 98, NT platforms and XP. This is one of the improved language efficiency from Basic
language. Visual basic includes a variety of open active control for user interface to design
application forms.
The user interface is the part of the program that responds to key press
and mouse clicks. The action is referred to as events of the form and a control in the form.
Controls are placed to communicate with backend database and validation checks. Visual basic
provides a vast properties and methods each control which helps utilize all the function for
record manipulations. Data manager in visual basic easy way to create database and build
interface using data control or data access object the database tables. Each database objects can
be accessed through data access object of any type as such as record set.
This record set contain record collection, can be efficiently, manipulated
using different record set methods such as add new and edit. Report generation is prepared,
using data report, which can be used to bring different types of report such as tabular report,
group report and query –based report.

6
IMPOTANT FEATURES IN VISUAL BASIC 6.0:
Active X control
 There are several built in active x control in VB6.0 they are used to represent the data
in a simple format.
 Tree view control - is used to represent the data in a hierarchical tree structure format.
 List view control – lists the data in a vertical table format.
 Animation control and multimedia control are mainly used in graphical oriented
application developed using VB6.0.
MS ACCESS
MS Access is a powerful database management system and user creates application that
requires little or no programming. It supports GUI features entire programming language, VBA
(Visual Basic 6 for application).
Access is easy enough to use that, in short time, beginners can manage their own data
in MS Access; the database means a collection of tables that holds data. It collect and stores all
the other related object such as queries, forms and report that are used to implement the
database management function effectively. The MS access database can acts as a backend
database for VB 6.0.
A user can move inside a table very easily using the navigating tools supported by the
Access database. A table can be accessed in number of ways like a snapshot, dynaset, table etc.

7
4. SYSTEM DESIGN
Design is the first stepping stone for the development of any system.
The process of system is very elaborate and should be carried with almost care as the actual
system get its shape at this phase. This consists of four main stages.
They are
1. Input design
2. Output design
3. Screen design
4. Code design
5. Database design
4.1. INPUT DESIGN:
The input design is the link between the information system and the
user. It comprises the director specification and procedures for data preparation and those
steps that are necessary to put transaction data into a usable form for processing data entry.
The activity if putting data in to the computer for processing can be achieved by inputs,
focuses on controlling the amount of inputs required, controlling errors, avoiding delay,
avoiding extra steps and keeping the process simple.
System analyst decides the following input design details:
1. Why data to input?
2. What medium is used?
3. How the data should be arranged or coded?
4. The dialog to guide users in providing input
5. Data item and transaction needing validation to detect errors
6. Methods for performing input validation and steps to follow when error occur.
.

8
4.2. OUTPUT DESIGN:
Computer output is the most important and direct source of information
to the user. Output design is a process that involves designing necessary output that have to be
given to various users according to their requirements. Efficient, intelligible output design will
improve the system relationship with the user and help indecision making. Since the reports
are directly required by the management for taking decision and to draw conclusion, they must
be designed with almost care to the user. The options for the output and report are given in the
system menu. When designing output, system analyst must accomplish the following:
1. Determine the information to present.
2. Determine whether to display, print, or “speak” the information and select the output
to intended receipts.
3. Arrange the present of information acceptable format.
4. Determine how to distribute the output to intended receipts.
4.3. SCREEN DESIGN:
Screen design begins with recognition that the screen is composed of different
areas. Layout tools assist the analyst in specifying the content of the signal and multiple
design formats. All screen have been provided with menus, push buttons facilities, a icons
and controls buttons such as Add/Delete/Update/Find/Clear/Exit etc. The main screen
consists of main menu from which we can move to another forms or screen. In designing
output screens we need area for:
1. Heading and titles.
2. The content of display.
3. Message and instructions.
4. Some times explanations for information in the report.

9
4.4. CODE DESIGN:
A code is a group of characters designed to identify the data items of the same
type uniquely. When hospital volume of data are handled , it is essential that each one
identified, selected and retrieved quickly and easily and there arises the need for the codes.
Codes should be designed carefully and should be meaningful. It should abide the general
rules of the code designing and should be understood by the user.
4.5. DATABASE DESIGN:
Database files are the key source of the information into the system. The final
design must satisfy user needs in terms of completeness, integrity, performance and other
factors. The main objective of the database design is to store the captured data efficiently and
facilitate its timely retrieval.

10
4.5 DESIGN NOTATIONS
4.5.1 System Flow Diagram
Login Process
Insurance Agency Management System
Introduction Client
Client Dairy
Policy
Client Details
Add Client
Payment
Policy Details
Payment Details
About Company
and Project
Exit

11
4.1.2 Data Flow Diagram
Level: 0 DFD
User
Login
In valid user
Valid user
Login
Checkin
g

12
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the
processes that change or transform data throughout a system. It is a structured analysis and
design tool that can be used for flowcharting in place of, or in association with, information
Introductio
n
Client Dairy
Client
Details
Level: 1 DFD
Add Client
Policy
Details
Payment Details
With Add Amount
Exit
Level: 2 DFD

13
oriented and process oriented system flowcharts. When analysts prepare the DFD, they specify
the user needs at a level of detail that virtually determines the information flow into and out of
the system and the required data resources. This network is constructed by using a set of
symbols that do not imply a physical implementation. The DFD reviews the current physical
system, prepares input and output specification, specifies the implementation plan etc., Four
basic symbols are used to construct data flow diagrams. They are symbols that represent data
source, data flows, and data transformations and data storage. The points at which data are
transformed are represented by enclosed figures, usually circles, which are called nodes.
A "Square" defines a source (originator) or destination of a system data.
An "Arrow" identifies data flow. It is a pipeline through which information flows.
A "Circle" represents a process that transforms incoming data flow(s) into outgoing data
flow(s).
An "Open Rectangle" is a data store.
Steps to Construct Data Flow Diagrams
Four steps are commonly used to construct a DFD
 Process should be named and numbered for easy reference. Each name should be
representative of the process.
 The direction of flow is from top to bottom and from left to right.
 When a process is exploded in to lower level details they are numbered.
 The names of data stores, sources and destinations are written in capital letters.

14
4.1.2 Table Design
Table Name: ClientDet
Primary Key: Sno
Description: Client Details
S.NO FIELD NAME DATATYPE FIELDWIDTH DESCRIPTION
1 Sno Number 8 Serial number
2 cname Text 10 Client Name
3 cProductName Text 15 Product Name
4 PolicyNo Number 15 Client Policy Number
5 PAdd Text 16 Client Permanent Address
6 Gen Text 6 Gender
7 Occup Text 15 Client Occupation
8 Buaddr Text 15 Client Business Address
9 Qual Text 15 Client Qualification
10 Nation Text 10 Nation
11 Religion Text 10 Religion
12 MStatus Text 4 Client Marital Status
13 NomineeName Text 15 Client Nominee Name
14 DOC Date 8 Date of Commencement
15 Taddr Text 15 Client Temporary Address
16 Phno Number 15 Client Phone Number
17 Age Number 2 Client Age

15
Table Name: AddClient
Primary Key: Sno
Description: Add Clients Details
1 Sno int 8 Serial number
2 cname varchar 10 Client Name
3 cProductName varchar 15 Product Name
4 PolicyNo int 15 Client Policy Number
5 PAdd varchar 16 Client Permanent Address
6 Gen varchar 6 Gender
7 Occup varchar 15 Client Occupation
8 Buaddr varchar 15 Client Business Address
9 Qual varchar 15 Client Qualification
10 Nation varchar 10 Nation
11 Religion varchar 10 Religion
12 MStatus varchar 4 Client Marital Status
13 NomineeName varchar 15 Client Nominee Name
14 DOC Date 8 Date of Commencement
15 Taddr varchar 15 Client Temporary Address
16 Phno int 15 Client Phone Number
17 Age int 2 Client Age
Table Name: PayDet
Primary Key: Sno
Description: Payment Details
1 Sno int 8 Serial number
2 cPolicyNo int 15 Client Policy Number
3 ModePay varchar 10 Mode of Payment
4 PolStatus varchar 15 Policy Status
5 DLastPay Date 8 Date of Last Payment
6 AmtLastPay int 16 Amount of Last Payment

16
Table Name: PolicyDet
Primary Key: Sno
Description: Policy Details
1 Sno Number 8 Serial number
2 cPolicyNo Number 15 Client Policy Number
3 Poltype Text 16 Client Policy Type
4 SumAssue Number 16 Sum Assured
5 DOCPol Date 8 Date of Commencement Policy
6 Term Number 2 Term
7 MaturityD Date 8 Maturity Date
8 PPaidTillD Date 8 Premium Paid Till Date
9 PreAmtDue Number 10 Premium Amount Due
10 ServiceTax Number 6 Service Tax
11 Educess Number 6 Education Cess
12 TotAmtDue Number 16 Total Amount Due
13 NxtPreDueD Date 8 Next Premium Amount Due
14 MOPay Text 10 Mode of Payment
15 PolStatus Text 10 Policy Status

17
5. SYSTEM TESTING
5.1 System Testing
Software testing is the process of executing the program with the sole interest
of finding an error. A good test is the one that a high probability of finding the yet undiscovered
error. This test focuses on each module separately assuring that it functions properly as a unit.
The enables users to detect errors and correct it without affecting any other
modules. Whenever the program was not executing the required function, it must be corrected
to get the required result. Thus all the modules, master, transaction, queries, reports, are tested
separately with test data. Errors isolated and corrected. To check error-handling paths,
uncorrected data is entered and tested.
5.1.1 Test Methodologies
Unit Testing
In this, each module of the program is tested individually to find out whether
retriever, manipulate and store any loss of data.
For example, machine code, company code and power generation hours won’t
negative or zero values, this condition was tested successfully by entering zero and negative
values. Similarly, if you want to input correct date you enter some other date system won’t
accept.
Validation
Data Validation is done to see whether the corresponding entries in different
tables done correctly. Proper validation checks are done in case of insertion and updating of
tables, in order, to see that no duplication of data has occurred. Validation succeeds when the
software functions in a manner as expected by the customer.
Interaction Testing
In this testing, all modules of the application are combined together and running
is made. This ensures the co-ordination between different modules of the program. This test

18
starts from main menu to all the modules. Form term main menu we can to the entire application
module and to the main module.
Output Testing
After performing the validation testing, the next step is output testing of the
proposed system, since no system could be useful if it does not produce the required output in
the specified format. The outputs generated or displayed by the system under consideration
are tested by asking the users about the format required by them. Hence the output format is
considered in 2 ways – one is on screen and another in printed format.

19
6. IMPLEMENTATION
Implementation is the stage of the project where the theoretical design is turned into a
working system. At this stage the main work load, the greatest upheaval and the major impact
on the existing system shifts to the user department. If the implementation is not carefully
planned a controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from the old
system to the new one. The new system may be totally new, replacing an existing manual or
automated system or it may be a major modification to an existing system. Proper
implementation is essential to provide a reliable system to meet the organization requirements.
Successful implementation may not guarantee improvement in the organization using the new
system, but improper installation will prevent it.
The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old system
to the new system. The system can be implemented only after thorough testing is done and if
it is found to be working according to the specifications. The system personnel checks the
feasibility of the system.
The most crucial stage is achieving a new successful system and giving confidence on
the new system for the user that it will work efficiently and effectively. It involves careful
planning, investigation of the current system and its constraints on implementation, design of
methods to achieve the changeover. The more complex the system being implemented, the
more involved will be the system analysis an the design effort required just for implementation.
The system implementation has three main aspects. They are education and training, system
testing and changeover.
The implementation stage involves following tasks.
 Careful planning.
 Investigation of system and constraints.
 Design of methods to achieve the changeover.
 Training of the staff in the changeover phase.

20
 Evaluation of the changeover method.
The method of implementation and the time scale to be adopted are found out initially.
Next the system is tested properly and the same time users are trained in the new procedures.
Implementation Procedures
Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system. In many
organizations some one who will not be operating it, will commission the software
development project. The people who are not sure that the software is meant to make their job
easier. In the initial stage, they doubt about the software but we have to ensure that the
resistance does not build up as one has to make sure that
 The active user must be aware of the benefits of using the system
 Their confidence in the software is built up
 Proper guidance be imparted to the user so that he is comfortable in using the
application.
Before going ahead and viewing the system, the user must know that for
viewing the result, the server program should be running in the server. If the server object is
not up running on the server, the actual processes wont take place.

21
6.1 SYSTEM MAINTANANCE
The maintenance phase of the software cycle is the time in which a Software product
performs useful work.
After a system is successfully implemented, it should be maintained in a proper manner.
System maintenance is an important aspect in the software development life cycle. The need
for system maintenance is for it to make adaptable to the changes in the system environment.
There may be social, technical and other environmental changes, which affects a system, which
is being implemented. Software product enhancements may involve providing new functional
capabilities, improving user displays and mode of interaction, upgrading the performance
characteristics of the system. So only through proper system maintenance procedures, the
system can be adapted to cope up with these changes.
Software maintenance is of course, far more than “finding mistakes”. We may define
maintenance by describing four activities that are undertaken to after a program is released for
use.
The first maintenance activity occurs because it is unreasonable to assume that software
testing will uncover all latent errors in a large software system. During the use of any large
program, errors will occur and be reported to the developer.
The process that includes the diagnosis and correction of one or more errors is called
corrective maintenance.
The second activity that contributes to a definition of maintenance occurs because of
the rapid change that is encountered in every aspect of computing. Therefore, adaptive
maintenance- an activity that modifies software to properly interfere with a changing
environment is both necessary and commonplace.
The third activity that may be applied to a definition of maintenance occurs when a
software package is successful. As the software is used, recommendations for new capabilities,
modifications to existing functions, and general enhancements are received from users. To

22
satisfy requests in this category, perfective maintenance is performed. This activity accounts
for the majority of all effort expended on software maintenance.
The fourth maintenance activity occurs when software is changed to improve future
maintainability or reliability, or to provide a better basis for future enhancements. Often called
preventive maintenance, this activity is characterized by reverse engineering and re-
engineering techniques.

23
7. CONCLUSION AND FUTURE ENHANCEMENT
The “POLICY MANAGEMENT SYSTEM” has been developed to fill all
the requirements of the Policy Agency. The system is tested with the sample data and found to
be executing at its maximum performance.
The system is fully user interactive with command buttons for selecting various
options to navigate other table processing and manipulate the effective handling of Client
Details and Payment Details. Report from the system provides complete details about the
Policy to the Policy Agency, hence the daily report taken so that any future change in the
current system will improve the efficiency of the generating process.
By using this software, they can take quick decisions and preventive actions
based on the details given by the system. Due to the software, I hope quality will be
improved, problems will be solved.
It is user friendly system provided with options, which can be utilized by the
desired operations. The new system overcomes the problems encountered with the old
system.

38
9.0 CODE
Code For Home Page
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub cmdstart_Click()
Load Addressform
Addressform.Show
End Sub
Private Sub Form_Load()
End Sub
Private Sub Timer1_Timer()
LBLDHARAM.BackColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
LBLDHARAM.ForeColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
End Sub
lblcollege.BackColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
lblcollege.ForeColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
End Sub
CODE FOR PRESENTATION1
lblaum.BackColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
lblaum.ForeColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
lblg.BackColor = RGB(Rnd * 200, Rnd * 200, Rnd * 200)
End Sub
Dim rsmove As ADODB.Recordset
Private Sub cmddelete_Click()
Dim cmd As New ADODB.Command

39
cmd.ActiveConnection = con
cmd.CommandText = "delete * from Addmission where Sno="
&Val(txtsno.Text)
Name = " & txtname.Text"
Fname = "& txtfname.Text"
Mname = " & txtmname.Text"
DOB = "&txtadmdate1.text"
Paddress = " & txtpadd.Text"
Taddress = " & txttadd.Text"
Qualification = "& txtqua.Text"
Coste = " &txtcoste.Text"
Class = "&txtclass.Text"
Sex = "& txtsex.Text"
Religion = "& txtrel.Text"
admno = "&Val(admno.Text)"
ADMDATE = "& Val(txtadmdate.text)"
Eone = "txteone.Text"
Etwo = "& txtetwo.Text"
Ethree = "&txtethree.Text"
Yone = "&Val(txtyone.Text)"
Ytwo = "&Val(txtytwo.Text)"
Ythree = "& Val(txtythree.Text)"
Uone = "& txtuone.Text"
Utwo = "& txtutwo.Text"
Uthree = "& txtuthree.Text"
Rone = "&txtrone.Text"
Rtwo = "&txtrtwo.Text"
Rthree = "& txtrthree.Text"
cmd.Execute
End Sub
Unload Me
End Sub

40
Private Sub cmdnext_Click()
rsmove.MoveNext
If rsmove.EOF Then
MsgBox "It is Last entry"
Else
txtsno.Text = rsmove.Fields("Sno")
txtname.Text = rsmove.Fields("NAME")
txtfname.Text = rsmove.Fields("Fname")
txtmname.Text = rsmove.Fields("Mname")
txtpadd.Text = rsmove.Fields("Paddress")
txttadd.Text = rsmove.Fields("Taddress")
txtqua.Text = rsmove.Fields("Qualification")
txtcoste.Text = rsmove.Fields("Coste")
txtclass.Text = rsmove.Fields("Class")
txtsex.Text = rsmove.Fields("Sex")
txtrel.Text = rsmove.Fields("Religion")
txtadmno.Text = rsmove.Fields("Admno")
txtadmdate.Text = rsmove.Fields("ADMDATE")
txteone.Text = rsmove.Fields("Eone")
txtetwo.Text = rsmove.Fields("Etwo")
txtethree.Text = rsmove.Fields("Ethree")
txtyone.Text = rsmove.Fields("Yone")
txtytwo.Text = rsmove.Fields("Ytwo")
txtythree.Text = rsmove.Fields("Ythree")
txtuone.Text = rsmove.Fields("Uone")
txtutwo.Text = rsmove.Fields("Utwo")
txtuthree.Text = rsmove.Fields("Uthree")
txtrone.Text = rsmove.Fields("Rone")
txtrtwo.Text = rsmove.Fields("Rtwo")
txtrthree.Text = rsmove.Fields("Rthree")
End If

41
End Sub
Private Sub cmdprevious_Click()
rsmove.MovePrevious
If rsmove.BOF Then
MsgBox " first"
Else
txtsno.Text = rsmove.Fields("Sno")
txtname.Text = rsmove.Fields("NAME")
txtfname.Text = rsmove.Fields("Fname")
txtmname.Text = rsmove.Fields("Mname")
txtpadd.Text = rsmove.Fields("Paddress")
txttadd.Text = rsmove.Fields("Taddress")
txtqua.Text = rsmove.Fields("Qualification")
txtcoste.Text = rsmove.Fields("Coste")
txtclass.Text = rsmove.Fields("Class")
txtsex.Text = rsmove.Fields("Sex")
txtrel.Text = rsmove.Fields("Religion")
txtadmno.Text = rsmove.Fields("Admno")
txtadmdate.Text = rsmove.Fields("ADMDATE")
txteone.Text = rsmove.Fields("Eone")
txtetwo.Text = rsmove.Fields("Etwo")
txtethree.Text = rsmove.Fields("Ethree")
txtyone.Text = rsmove.Fields("Yone")
txtytwo.Text = rsmove.Fields("Ytwo")
txtythree.Text = rsmove.Fields("Ythree")
txtuone.Text = rsmove.Fields("Uone")
txtutwo.Text = rsmove.Fields("Utwo")
txtuthree.Text = rsmove.Fields("Uthree")
txtrone.Text = rsmove.Fields("Rone")
txtrtwo.Text = rsmove.Fields("Rtwo")
txtrthree.Text = rsmove.Fields("Rthree")
End If
End Sub

42
Private Sub cmdrefresh_Click()
txtsno.Text = ""
txtname.Text = ""
txtfname.Text = ""
txtmname.Text = ""
txtpadd.Text = ""
txttadd.Text = ""
txtqua.Text = ""
txtcoste.Text = ""
txtclass.Text = ""
txtsex.Text = ""
txtrel.Text = ""
txtadmno.Text = ""
txtadmdate.Text = ""
txteone.Text = ""
txtetwo.Text = ""
txtethree.Text = ""
txtyone.Text = ""
txtytwo.Text = ""
txtythree.Text = ""
txtuone.Text = ""
txtutwo.Text = ""
txtuthree.Text = ""
txtrone.Text = ""
txtrtwo.Text = ""
txtrthree.Text = ""
End Sub
Private Sub cmdsave_Click()
Dim rsmain As New ADODB.Recordset
rsmain.Open "select*from Addmission where Sno=" & Val(txtsno.Text) & "", con, 1, 2
If rsmain.RecordCount <> 0 Then
rsmain.MoveFirst

43
Else
rsmain.AddNew
End If
rsmain.Fields("Sno") = Val(txtsno.Text)
rsmain.Fields("NAME") = txtname.Text
rsmain.Fields("Fname") = txtfname.Text
rsmain.Fields("Mname") = txtmname.Text
rsmain.Fields("Paddress") = txtpadd.Text
rsmain.Fields("Taddress") = txttadd.Text
rsmain.Fields("Qualification") = txtqua.Text
rsmain.Fields("Coste") = txtcoste.Text
rsmain.Fields("Class") = txtclass.Text
rsmain.Fields("Sex") = txtsex.Text
rsmain.Fields("Religion") = txtrel.Text
rsmain.Fields("Admno") = Val(txtadmno.Text)
rsmain.Fields("ADMDATE") = Val(txtadmdate.Text)
rsmain.Fields("Eone") = txteone.Text
rsmain.Fields("Etwo") = txtetwo.Text
rsmain.Fields("Ethree") = txtethree.Text
rsmain.Fields("Yone") = Val(txtyone.Text)
rsmain.Fields("Ytwo") = Val(txtytwo.Text)
rsmain.Fields("Ythree") = Val(txtythree.Text)
rsmain.Fields("Uone") = txtuone.Text
rsmain.Fields("Utwo") = txtutwo.Text
rsmain.Fields("Uthree") = txtuthree.Text
rsmain.Fields("Rone") = txtrone.Text
rsmain.Fields("Rtwo") = txtrtwo.Text
rsmain.Fields("Rthree") = txtrthree.Text
rsmain.Update
End Sub
Private Sub Form_Load()
Set rsmove = New ADODB.Recordset
rsmove.Open "select*from Addmission", con, 1, 2
rsmove.MoveLast

44
End Sub
Private Sub txtadmno_Change()
If KeyAscii <> 8 Then
If KeyAscii < 48 Or KeyAscii > 57 Then
KeyAscii = 0
End If
End If
End Sub
Private Sub txtsno_KeyPress(KeyAscii As Integer)
KeyAscii = 0
End If
End If
End Sub
Private Sub txtyone_KeyPress(KeyAscii As Integer)
KeyAscii = 0
End If
End If
End Sub
Private Sub txtythree_KeyPress(KeyAscii As Integer)
KeyAscii = 0
End If
End If
End Sub
Private Sub txtytwo_KeyPress(KeyAscii As Integer)

45
KeyAscii = 0
End If
End If
End Sub
CODS FOR FEESDETAIL
Dim rsmove As ADODB.Recordset
Private Sub cmddelete_Click()
Dim cmd As New ADODB.Command
cmd.ActiveConnection = con
cmd.CommandText = "delete * from Fessdetail where SNO=" & Val(txtsno.Text)
BOOKNAME = " & txtbookname.Text"
BOOKPRICE = " & val(txtbookprice.Text)"
STUNAME = "& txtname.Text"
FATHERNAME = "& txtfname.Text"
DOB = "& Val(txtdob.Text)"
ADDRESS = "& txtadd.Text"
STUPHONE = "& Val(txtphone.Text)"
COURSENAME = "&txtcname.Text"
NAMEOFMONTH = "& txtmoname.Text"
TOTALFEES = "&Val(txttfees.Text)"
PAIDFEES = "& Val (txtpfees.Text)"
BALANCEFEES = "& Val(txtbfees.Text)"
cmd.Execute
End Sub
Unload Me
End Sub
Private Sub cmdnext_Click()

46
On Error GoTo errh
rsmove.MoveNext
If rsmove.EOF Then
MsgBox " This is last entry"
Else
txtsno.Text = rsmove.Fields("SNO")
txtname.Text = rsmove.Fields("STUNAME")
txtfname.Text = rsmove.Fields("FATHERNAME")
txtdob.Text = rsmove.Fields("Dob")
txtadd.Text = rsmove.Fields("ADDRESS")
txtphone.Text = rsmove.Fields("STUPHONE")
txtcname.Text = rsmove.Fields("COURSENAME")
txtmoname.Text = rsmove.Fields("NAMEOFMONTH")
txttfees.Text = rsmove.Fields("TOTALFEES")
txtpfees.Text = rsmove.Fields("PAIDFEES")
txtbfees.Text = rsmove.Fields("BALANCEFEES")
End If
Exit Sub
MsgBox Err.Description
End Sub
Private Sub cmdprevious_Click()
On Error GoTo errh
rsmove.MovePrevious
If rsmove.BOF Then
MsgBox "This is First entry"
Else
txtsno.Text = rsmove.Fields("SNO")
txtname.Text = rsmove.Fields("STUNAME")
txtfname.Text = rsmove.Fields("FATHERNAME")
txtdob.Text = rsmove.Fields("Dob")

47
txtadd.Text = rsmove.Fields("ADDRESS")
txtphone.Text = rsmove.Fields("STUPHONE")
txtcname.Text = rsmove.Fields("COURSENAME")
txtmoname.Text = rsmove.Fields("NAMEOFMONTH")
txttfees.Text = rsmove.Fields("TOTALFEES")
txtpfees.Text = rsmove.Fields("PAIDFEES")
txtbfees.Text = rsmove.Fields("BALANCEFEES")
End If
Exit Sub
errh:
MsgBox Err.Description
End Sub
Private Sub cmdrefresh_Click()
txtsno.Text = ""
txtname.Text = ""
txtfname.Text = ""
txtdob.Text = ""
txtadd.Text = ""
txtphone.Text = ""
txtcname.Text = ""
txtmoname.Text = ""
txttfees.Text = ""
txtpfees.Text = ""
txtbfees.Text = ""
End Sub
Private Sub cmdsave_Click()
Dim rsmain As New ADODB.Recordset
rsmain.Open "select*from Fessdetail where Sno=" & Val(txtsno.Text) & "", con, 1, 2
If rsmain.RecordCount <> 0 Then
rsmain.MoveFirst
Else
rsmain.AddNew
End If

48
Reference
Acharya, Kamal. "STUDENT INFORMATION MANAGEMENT
SYSTEM." Authorea Preprints (2023).
Acharya, Kamal. "Library Management System." Available at SSRN4807104 (2019).
ACHARYA, KAMAL, et al. "LIBRARY MANAGEMENT SYSTEM." (2019).
Acharya, Kamal. "Online bus reservation system project report." Authorea
Preprints (2024).
Acharya, Kamal. "Online bus reservation system project report." (2024).
Acharya, Kamal. “Online Bus Reservation System.” SSRN ElectroNIC ASIA
Journal (2024): n. pag.
Acharya, Kamal. “Student Information Management System Project.” SSRN
ElectroNIC ASIA Journal (2024): n. pag.
Acharya, Kamal. “ATTENDANCE MANAGEMENT SYSTEM.” International
Research Journal of Modernization in Engineering Technology and
Science (2023): n. pag.
Acharya, Kamal. “College Information Management System.” SSRN ElectroNIC
ASIA Journal (2024): n. pag.
Acharya, Kamal, Attendance Management System Project (April 28, 2024).
Available at
SSRN: https://ssrn.com/abstract=4810251 or http://dx.doi.org/10.2139/ssrn.4810251
Acharya, Kamal, Online Food Order System (May 2, 2024). Available at
Acharya, Kamal, University management system project. (May 1, 2024). Availableat
Acharya, Kamal, Online banking management system. (May 1, 2024). Available at
Acharya, Kamal, Online Job Portal Management System (May 5, 2024). Available at
Acharya, Kamal, Employee leave management system. (May 7, 2024). Available
at
Acharya, Kamal, Online electricity billing project report. (May 7, 2024). Available at

Policy management system project report.pdf

Recommended

Recommended

More Related Content

Similar to Policy management system project report.pdf

Similar to Policy management system project report.pdf (20)

More from Kamal Acharya

More from Kamal Acharya (20)

Recently uploaded

Recently uploaded (20)

Policy management system project report.pdf