SYNOPSIS

SYNOPSIS OF THE PROJECT

This project can manage all information about student, books it

also maintains the information about issue and return details of books
and if a student not return before proper date then it will apply fine
and it helps to search records quickly and generate electronic report
within a second. I would like to extend my sincere thanks to of
“college” who made available all possible resources necessary for my
project. Further i would like to give regards to who had given their
kind time towards my project. Finally, i would give my whole-hearted
thanks for providing all necessary required data for the project.
 INDEX

 Main Report
 Objectives & Scope of the project
 Theoretical Background of Project
 Definition of problem
 System Analysis & Design
 System Planning (PERT Chart)
 Methodology adopted, system Implementation & Detail of
Hardware & Software used.
 System maintenance & Evaluation.
 Cost and benefit Analysis
 Detailed Life Cycle of the project
 ERD,DFD
 Input and Output Screen Design
 Process involved
 Methodology used for testing
 Test Report, Printout of the code sheet
 User/Operational Manual- including security aspects, access
rights,
 back up, Controls etc.
 Conclusion
 References
 Soft copy of the project on CD
 OBJECTIVE OF THE PROJECT

There are so many disadvantages in the existing system because

they want to a log of paper work in the system and many people
engage to maintain of the system. But the technology is growing fatly
and researches a new technology.
So the cost of the control is very less and we also find previous
information in a few seconds on the computerization by this Software. It
improve efficiency of their bill according to the customer satisfaction.
The major objective for implementing a computerized Sofware in
an organization is:-
 To manage the resources of the Stock efficiently.
 To reduce the losses incurred due to wrong entries.
 To manage the Customer/member data in a proper manner.
 Also, manage the asset.
 To maintain the daily expense in efficient manner.
 Preparation of various analysis reports.
 Generation of report that help management for making effective
and
 timely decisions.
So what benefits can a organization gain from implementing a
project solution like it?

Tracking: Tracking the progress of your projects and programs is

important for the long term success of your business. A project
management software system will give you the visibility to see if a
project is running to its predetermined time frame, what has been done
and what still needs to be complete. The software reduces the need for
paper or electronic updates from the project team members to their
project manager.
Resourcing: The project management system ensures that the optimal
resources are working on the right projects by examining the level of
skills and abilities needed to successfully complete the project.
Assigning resources to tasks or projects through the project
management system will ensure that each resource knows all the
information needed for them to complete the project.

Communication: A project management system makes communication

channels regarding tasks, projects and programs easier through the
uploading and sharing of files, collaborating on an online space and
emailing updates through the system. Communication channels with
your customers/ clients can be made simpler also as business
documents e.g. invoices can be sent directly from the project
management system to its required destination and information on
those customers/ clients can be kept on a virtual database to help with
the follow up process that takes place.

Financial Control: A critical item in the management of projects is the

budget and the way in which the budget is managed could ultimately
decide the future of the business. The project management software
gives the project manager a visual on the project costs, project budget
(actual Vs planned), project cost data etc to ensure that projects and
programs run to their assigned budgets, money is ultimately saved and
not lost and generating a clear Return on Investment (ROI) on all
projects.

Where are we now?: A PM software solution can easily tell an

organization if they are in line with their initial requirements by taking a
snapshot of the project at that point in time and examining some of the
following:

Who is working on each task or project

Is there any time delays
Is the project keeping to its budget etc
Decision Making: When making a decision in project management all
aspects of the project need to be taken into consideration. By using a
project management system the decision making process is improved,
as the information is all in clearly presented in one place.

The Edge: By having a project management system in place it could

ultimately give you a competitive edge over your competitors. If you
can complete a project more efficiently than the rest you it can give you
that extra push ahead of your competitors.

Risk management: Out of nowhere a risk can throw a spanner in the

works and cause severe problems resulting in the project failing.
Project management software system can give you a platform by which
risks can be flagged, tracked and correctly resolved to ensure that the
risk has the lowest possible negative effect on the project.

Quality of information: The quality of the information is increased as

only the information that’s needed is gathered and shown.
Keeping the boss happy: Ok this won’t provide the company with
benefits however it will give you some peace and reassurance at your
next meeting with the boss. The project management system provides
you with all the tools to help your project come in on time and too
budget keeping all involved happy.

.
 SCOPE OF THE PROJECT

The scope of the project includes that what all future enhancements
can be done in this system to make it more feasible to use :
 Databases for different products range and storage can be
provided.
 Multilingual support can be provided so that it can be
understandable by the person of any language.
 More graphics can be added to make it more user- friendly and
understandable.
 Manage and backup versions of documents online.

Scope creep management is important for effective project

management. Projects are expected to meet strict deadlines with
resource restraints, and an unvetted and unapproved change in the
scope can affect the success of the project. Scope creep sometimes
causes cost overrun.

Scope creep is a term which refers to the incremental expansion of the

scope of a project, which may include and introduce more requirements
that may not have been a part of the initial planning of the project, while
nevertheless failing to adjust schedule and budget. There are two
distinct ways to separate scope creep management. The first is
business scope creep, and the second is called features (also
technology) scope creep. The type of scope creep management is
always dependent on the people who create the changes.

Business scope creep occurs when decisions that are made with
reference to a project are designed to solve or meet the requirements
and needs of the business. Business scope creep changes may be a
result of poor requirements definition early in development, or the
failure to include the users of the project until the later stage of the
systems development life cycle. Management system. Items deemed
out of scope go directly through the change control process and are not
automatically added to the project work items. The Project Scope
Management plan is included in as one of the sections in the overall
Project Management plan. It can be very detailed and formal or loosely
framed and informal depending on the communication needs of the
project.

Features (Technology) scope creep occurs when the scope creep is

introduced by technologists adding features not originally contemplated.
Customer-pleasing scope creep occurs when the desire to please the
customer through additional product features adds more work to the
current project rather than to a new project proposal. Gold-plating
scope creep occurs when technologists augment the original
requirements because of a bias toward "technical perfectionism" or
because the initial requirements were insufficiently clear or detailed.
 THEORETICAL BACKGROUND OF THE
PROJECT

FRONT END (VB 6.0)

Visual basic 6.0 is the popular version of the programming language.

This environment is to develop robust. Attend alone application and
utilities is less time then it usually takes in other language. Project
development has been all easier what with the language supporting the
oops concept.

VISUAL BASIC is a VISUAL and Event-driven Programming

Language. These are the main divergence from the old BASIC. In
BASIC, programming is done in a text-only environment and the
program is executed sequentially. In VB6, programming is done in a
graphical environment. In the old BASIC, you have to write program
code for each graphical object you wish to display it on screen,
including its position and its color. However, In VB6 , you just need to
drag and drop any graphical object anywhere on the form, and you can
change its properties using the properties window.

In addition, Visual Basic 6 is Event-driven because we need to write

code in order to perform some tasks in response to certain events. The
events usually comprise but not limited to the user's inputs. Some of the
events are load, click, double click, drag and drop, pressing the keys
and more. We will learn more about events in later lessons. Therefore,
a VB6 Program is made up of many subprograms, each has its own
program code, and each can be executed independently and at the
same time each can be linked together in one way or another.
 BACK END (MS ACCESS-2003)
Ms access is a dbms .a database system is basically a computer
based record keeping system. The collection of data, usually referred to
as the database, contains information about one particular enterprise. It
maintains any information be necessary to the decision making process
involved the management of that organization.
Very simply, Microsoft Access is an information management tool
that helps you store information for reference, reporting, and analysis.
Microsoft Access helps you analyze large amounts of information, and
manage related data more efficiently than Microsoft Excel or other
spreadsheet applications. This article shows you when to use Access,
and how it can help make you more effective.
Microsoft Access works in the same manner any database does,
by storing related information together, and letting you create
connections (commonly called relationships) between different things.
The relationships between two different things in MSAccess can be
very simple (such as a contact at a customer and the customer itself) or
complex. In the example below, the blue boxes represent the major
things we're tracking in our MS Access database tables, and the reports
at right show how you can join the related information for analysis and
reporting.
 DEFINITION OF PROBLEM

As we know manual system are quite tedious, time

consuming and less efficient and accurate in comparison to
the computerized system. So following are some advantages
of the old system:

1. Time consuming
2. Less accurate
3. Less efficient
4. Lots of paper work
5. Slow data processing
6. Not user friendly environment
7. Difficult to keep old records
8. Paper Work
SYSTEM ANALYSIS

AND

DESIGN
 SYSTEM ANALYSIS AND DESIGN

FEASIBILITY STUDY:-

An initial investigation terminates in a proposal that determines

whether an alternative system is feasible. Feasibility study can be
categorized into three major parts: -

(1) TECHNICAL FEASIBILITY:-

 The proposed system has technical capacity of required to

hold the data.
 This project is efficient and responds quickly for various
enquires regardless
 Of number of locations.
 The system proposed could be expanded easily and
Efficiency, whenever required.

(2) OPERATING FEASIBILITY STUDY:-

The management of the organization has a fully

supported us to bring up the project and the data security in
this project provided by setting up the password procedure so
that only the authorized user can access the system.

(3) OUR PROJECT IS ECONOMICAL FEASIBLE AS:-

* It has computerized paper works and also is reduced to

large extent
* With the help of this project single person is now available
to do the tasks of 5 to 7 persons.
* Due to processing speed of then Computer, we can
extract desired information’s in a fraction of second.
PERT CHART
 SYSTEM PLANNING (PERT CHART)

A PERT chart is a project management tool used to schedule,

organize, and coordinate tasks within a project. PERT stands
for Program Evaluation Review Technique, a methodology
developed by the U.S. Navy in the 1950s to manage the Polaris
submarine missile program. A similar methodology, the Critical Path
Method (CPM) was developed for project management in the private
sector at about the same time.
 A PERT chart presents a graphic illustration of a project as a
network diagram consisting of numbered nodes (either circles or
rectangles) representing events, or milestones in the project linked by
labelled vectors (directional lines) representing tasks in the project. The
direction of the arrows on the lines indicates the sequence of tasks. In
the diagram, for example, the tasks between nodes 1, 2, 4, 8, and 10
must be completed in sequence. These are
called dependent or serial tasks. The tasks between nodes 1 and 2,
and nodes 1 and 3 are not dependent on the completion of one to start
the other and can be undertaken simultaneously. These tasks are
called parallel or concurrent tasks. Tasks that must be completed in
sequence but that don't require resources or completion time are
considered to have event dependency. These are represented by
dotted lines with arrows and are called dummy activities. For example,
the dashed arrow linking nodes 6 and 9 indicates that the system files
must be converted before the user test can take place, but that the
resources and time required to prepare for the user test (writing the
user manual and user training) are on another path. Numbers on the
opposite sides of the vectors indicate the time allotted for the task.
The PERT chart is sometimes preferred over the Gantt chart,
another popular project management charting method, because it
clearly illustrates task dependencies. On the other hand, the PERT
chart can be much more difficult to interpret, especially on complex
projects. Frequently, project managers use both techniques.
 HARDWARE AND SOFTWARE USED

 HARDWARE USED:-

 PROCESSOR - PENTIUM-IV 945 GHZ

 RAM – 1 GB
 HARD DISK – 160 GB
 MONITOR – 17” SAMSUNG COLOR MONITOR
 DVD WRITER SONY
 KEYBOARD – 1.5 KEY MULTIMEDIA KEYBOARD
 PRINTER – HP LASER JET 6L PRINTER
 MOUSE – OPTICAL MOUSE IBALL

 SOFTWARE USED:-

 OPERATING SYSTEM – windows 7

 DATABASE – MS- ACCESS 2003
 FRONT-END PACKAGE – VISUAL BASIC 6.0
 COST AND BENEFIT ANALYSIS

Cost and Benefit Categories

In developing cost estimates for a system, we need to consider several
cost elements. Among them is hardware, personnel, facility, operating,
and supply cost.

1 Hardware cost relate to actual purchase or lease of the

computer and peripherals. Determining the actual cost of
hardware is generally more difficult when the system is shared
by various users than for a dedicated stand-alone system. In
some cases, the best way to control for this cost is to treat it is
an operating cost.
2 Personnel cost include EDP staff salaries and benefits as well
as pay for those involved in developing the system.
3 Facility costs are expenses incurred in the preparation of the
physical site where the application or the computer will be in
operation. This includes wiring, flooring, acoustics, lighting,
and air conditioning. These cost are treated as one time cost
and incorporated into the overall cost estimate of the candidate
system.
4 Operating cost include all cost associated with the day to day
operation of the system, the amount depends on the number of
shifts, the nature of the application, and the caliber of the
operating staff. There are various ways of covering operating
cost one approach is to treat operating cost as overhead.
Another approach is to charge each authorized user for the
amount of processing they request from the system. The
amount charged is based on computer time, staff time, and
volume of output produced. In any case, some accounting is
necessary to determine how operating cost should be handled.
5 Supply costs are variable costs that increase with increased
use of paper, ribbons, disks, and the like. They should be
estimated and included in the overall cost of the system.
 DETAILED LIFE CYCLE OF THE PROJECT

All stages of a software process status quo, problem definition,

technical development, and solution integration coexist simultaneously
at some level of detail. design and analysis. Information engineering
encompasses requirements gathering at the strategic business level
and at the business area level.

Software requirements analysis. The requirements gathering process

is intensified and focused specifically on software. To understand the
nature of the program(s) to be built, the software engineer ("analyst")
must understand the information domain
for the software, as well as required function, behavior, performance,
and interface. Requirements for both the system and the software are
documented
and reviewed with the customer.

Design. Software design is actually a multiuse process that focuses on

four distinct
attributes of a program: data structure, software architecture, interface
representations,
and procedural (algorithmic) detail. The design process translates
requirements into a representation of the software that can be
assessed for quality before coding begins. Like requirements, the
design is documented and becomes part of the software
configuration.

Code generation. The design must be translated into a machine-

readable form. The code generation step performs this task. If design is
performed in a detailed manner, code generation can be accomplished
mechanistically.

Testing. Once code has been generated, program testing begins. The
testing process focuses on the logical internals of the software,
ensuring that all statements have been tested, and on the functional
externals; that is, conducting tests to uncover errors and ensure that
defined input will produce actual results that agree with required results.

Implementation. Software will undoubtedly undergo change after it is

delivered to the customer (a possible exception is embedded software).
Change will occur because errors have been encountered, because the
software must be adapted to accommodate changes in its external
environment (e.g., a change required because of a new operating
system or peripheral device), or because the customer requires
functional or performance enhancements. Software
support/maintenance reapplies each of the preceding phases to an

existing program rather than a new one.

FIG. SDLC PHASE
ER DIAGRAM
 E-R DIAGRAM

Conceptual ERD Symbols

These symbols are generally used for conceptual data models,
although some aspects may spill over into logical data models. They
can be found in the UML Entity Relationship and Entity Relationship
shape libary of Lucidchart. If you don't see the shape you need, use an
image file (Lucidchart supports .PNG, .JPG, or .SVG import) or create
your own with our existing shapes and styling options.

ENTITIES
Entities are objects or concepts that represent important data. They are
typically nouns, e.g. customer, supervisor, location, or promotion.
Strong entities exist independently from other entity types. They always
possess one or more attributes that uniquely distinguish each
occurrence of the entity.

Weak entities depend on some other entity type. They don't possess
unique attributes (also known as a primary key) and have no meaning
in the diagram without depending on another entity. This other entity is
known as the owner.
Associative entities are entities that associate the instances of one or
more entity types. They also contain attributes that are unique to the
relationship between those entity instances.

RELATIONSHIPS
Relationships are meaningful associations between or among entities.
They are usually verbs, e.g. assign, associate, or track. A relationship
provides useful information that could not be discerned with just the
entity types.
Weak relationships, or identifying relationships, are connections that
exist between a weak entity type and its owner.
ATTRIBUTES
Attributes are characteristics of either an entity, a many-to-many
relationship, or a one-to-one relationship.
Multivalued attributes are those that are capable of taking on more
than one value.
Derived attributes are attributes whose value can be calculated from
related attribute values.
 Subject

auther

Avl_qt
y

Tname

BOOK

Dat
Dat e
e return
ISSU qty
qty ED

id
id

Student
Name

Class

Sport Phone
DATA DICTIONARY
DATA DICTIONARY
Subject Name Table

Book name Table

Student Table

Issue Table

Return Table
DFD
 DATA FLOW DIAGRAM
DFD is a graphical representation of data process and files used
in a support system.Data Flow Diagrams are useful tools for analyzing
existing systems. Data Flow Diagram is a network that describes flows
of data and the processes that changes or transforms the data
throughout a system.
Data flow diagrams can be expanded to show successive levels of
details sufficient.
Expansion should be performed during the initial investigation to
be certain that both the analyst and user personnel share a common
understanding of the existing system and its data flow.
The different symbols used in the data flow diagram are:-

1. Circle It is used form transfer the input to output

Indicate process that transfer data
flow.

2. Rectangle with When data is in file this symbol is

used flow.
Representation
Open End

3. Square Squares indicates the source of

destination .

4. Arrows Arrows are sued to show flow of path from

where it is coming & going.
Student

Subject Detail

Student

Register

Issue_tbl

Book_Detail

Issue book Return_tbl

Return book and

generate report
INPUT AND OUTPUT SCREEN DESIGN
Login Form
Mdi Form
Subject Entry Form
Book Entry Form
Student Entry Form

Issue Entry Form

Return Entry Form
Subject Report

Book Report
Student Report

Issue Report
Return Report
 PROCESS INVOLVED
WaterFall Model:The stages of “The Waterfall Model” are:

Requirement Gathering & Analysis:-This is the starting phase of the SDLC

in which all possible system requirements are captured & analyzed. Software
requirements specification includes the complete information about how
actual end users are expecting from the system. This document covers all
the necessary requirements for the development of project. Finally after
completion of requirement gathering & analysis (validation of requirement
against the user needs), a Requirement Specification document is created
which give out as a input to the next phase of SDLC. In this model once we
moved to the next phase then it won’t possible to add or update the
requirements.
System & Software Design: Prior to start actual coding, it is mandatory to
be aware of what all features we are going to implement & how it would look
like? The requirement specifications document created in the first phase is
used as the input to this phase & based on this the system design
specifications would be prepared. In which all hardware & system
requirements would be specified. The system design specifications
document prepared in this phase is used as input for the Implementation &
Testing phase model.
Implementation & Unit Testing: Upon getting the system design
specifications document the actual coding would be started. Before starting
the actual coding requirements are divided into the models/units. In the
actual coding the initially develop the small programs called units. After
implementing all units the integration would be started in the next phase. The
developed unit’s model functionality is tested separately in this phase to
check whether the unit models are meets the specified requirements & this
individual model testing is called as Unit Testing.
Integration & System Testing: In the previous model the system
requirements are divided into models & each model is developed & tested
separately. In this phase all units are integrated & done the system testing to
check whether the all models/units are integrated properly or not & the
system as whole doing as mention as per the system requirement document,
so we call this phase as the Integration & System Testing. Upon complete
testing of software is done then actual Software is successfully send to
customer.
Operations & Maintenance: This phase is the never ending phase of the
Waterfall Model. The problems are comes in picture after Implementation &
Unit Testing phase. The issues found after the implementation phase i.e.
not found in the period of the development life cycle. Some of the issues are
not catch after testing cycle done so those are implemented in the
maintenance phase, so this phase is called as Operations & Maintenance
phase.
Advantages of Waterfall Model:
 This is linear simple model to implement & easy to maintain.
 In the SDLC initial phase spent time on reviewing requirements and
design which saves the time later.
 Required resources are minimum in this model as compare to other.
 After every phase of the model a document in created which help &
simpler to understand & design the system.
 Upon completion of coding, is done to check for implemented code or
correctness of system.
 For each stage deadlines can be set which will help to develop the
system on decided time frame.

Disadvantages of Waterfall Model:

 The biggest disadvantages of such system is it won’t allow to go back.
If the problems in the design phase which creates complication in the
implementation phase.
 This model is rigid model. Not flexible & make changes is not possible
in the development of system.
 Unable to start the next phase before completing the previous phase
so time consuming.
 In the deployment phase all requirements are not covered or all
requirements are not cover so adding such requirements may create
unsuitable system.
 To make it customer happy such new requirement need to be
implemented in new version of system which leads to added cost to
system development.
 METHODOLOGY USED FOR TESTING
Testing Methodologies
As software applications get ever more complex and intertwined and
with the large number of different platforms and devices that need to
get tested, it is more important than ever to have a robust testing
methodology for making sure that software products/systems being
developed have been fully tested to make sure they meet their
specified requirements and can successfully operate in all the
anticipated environments with the required usability and security.
This page describes the various components of a thorough testing
methodology and illustrates how SpiraTest is best suited to help you
implement and manage them on your projects.

SpiraTest® manages your project's requirements, test cases, bugs and

issues in one integrated environment, with full traceability throughout
the testing lifecycle.
It is a complete solution that includes requirements
management, test ,release management and defect tracking all fully
integrated from day one.
Highly intuitive web application that provides a complete picture of a
project’s status and health yet requires only a web-browser.
Ability to leverage your existing technology
investments. SpiraTestintegrates with many automated testing
solutions and third-party defect-management systems.
Functional Testing
The functional testing part of a testing methodology is typically broken
down into four components - unit testing, integration testing, system
testing and acceptance testing – usually executed in this order. Each of
them is described below:
Unit Testing
The Unit testing part of a testing methodology is the testing of individual
software modules or components that make up an application or
system.These tests are usually written by the developers of the module
and in a test-driven-development methodology (such as Agile, Scrum or
XP) they are actually written before the module is created as part of the
specification. Eachmodule function is tested by a specific unit test
fixture written in the same programming language as the module.
Integration Testing
The Integration testing part of a testing methodology is the testing of
the different modules/components that have been successfully unit
tested when integrated together to perform specific tasks and activities
(also known as scenario testing). This testing is usually done with a
combination ofautomated functional tests and manual testing
depending on how easy it is to create automated tests for specific
integrated components.
SpiraTest includes support for storing, managing and coordinating
integration tests across various modules and components. With its
library of plugins and extensions for different automated functional
testing tools including ourRapise automation platform, SpiraTest is the
perfect solution for managing your integration testing.
System Testing
The system testing part of a testing methodology involves testing the
entire system for errors and bugs. This test is carried out by
interfacing thehardware and software components of the entire
system (that have been previously unit tested and integration tested),
and then testing it as a whole. This testing is listed under the black-box
testing method, where the software is checked for user-expected
working conditions as well as potential exception and edge conditions.
Acceptance Testing
The acceptance testing part of a testing methodology is the final phase
of functional software testing and involves making sure that all the
product/project requirements have been met and that the end-users
and customers have tested the system to make sure it operates as
expected andmeets all their defined requirements:
Performance, Load, Stress Testing
There are several different types of performance testing in most testing
methodologies, for example: performance testing is measuring how a
system behaves under an increasing load (both numbers of users and
data volumes), load testing is verifying that the system can operate at
the required response times when subjected to its expected load, and
stress testing is finding the failure point(s) in the system when the
tested load exceeds that which it can support.
 SOURCE CODE
Login Form

Private Sub Command1_Click()

If Text1.Text = "student" And Text2.Text = "student” Then
mdi.Show
Unload Me
Else
MsgBox "Invalid password", vbInformation
End If
End Sub
Private Sub Command2_Click()
End
End Sub

MDI Form

Private Sub addnew_Click()

Form1.Show
End Sub

Private Sub C_Click()

Form2..Show
End Sub

Private Sub crepor_Click()

DataReport1.Show
End Sub

Private Sub d_Click()

Form3.Show
End Sub

Private Sub e_Click()

End
End Sub

Private Sub Form_Load()

End Sub

Private Sub p_Click()

Form4.Show
End Sub

Private Sub pr_Click()

Form5.Show
End Sub

Private Sub PE_Click()

Form6.Show
End Sub

Private Sub purreport_Click()

DataReport4.Show
End Sub

Private Sub S_Click()

Form7.Show
End Sub

Private Sub SR_Click()

Form8.Show
End Sub

Private Sub salereort_Click()

DataReport5.Show
End Sub

Private Sub stockre_Click()

DataReport3.Show
End Sub
Subject Form

Private Sub Command1_Click()

Adodc1.Recordset.Update
MsgBox "Record saved.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.addnew
Text4.Text = Adodc1.Recordset.RecordCount + 1
End Sub
Private Sub Command4_Click()
Adodc1.Recordset.Update
MsgBox "Record Updated.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command5_Click()
Adodc1.Recordset.Delete
MsgBox "Record Deleed.", vbInformation
Adodc1.Refresh
End Sub
Private Sub DataCombo2_LostFocus()
Adodc3.Recordset.Find ("itemname='" & DataCombo2.Text & "'")
Text2.Text = Adodc3.Recordset(2)
End Sub
Private Sub Text1_LostFocus()
Text3.Text = Val(Text2.Text) * Val(Text1.Text)
End Sub
Student ENTRY Form

Private Sub Command1_Click()

Adodc1.Recordset.Update
MsgBox "Record saved.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.addnew
Text4.Text = Adodc1.Recordset.RecordCount + 1
End Sub
Private Sub Command4_Click()
Adodc1.Recordset.Update
MsgBox "Record Updated.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command5_Click()
Adodc1.Recordset.Delete
MsgBox "Record Deleed.", vbInformation
Adodc1.Refresh
End Sub
Private Sub DataCombo2_LostFocus()
Adodc3.Recordset.Find ("itemname='" & DataCombo2.Text & "'")
Text2.Text = Adodc3.Recordset(2)
End Sub
Private Sub Text1_LostFocus()
Text3.Text = Val(Text2.Text) * Val(Text1.Text)
End Sub
ISSUE ENTRY Form

Private Sub Command1_Click()

Adodc1.Recordset.Update
MsgBox "Record saved.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.addnew
Text4.Text = Adodc1.Recordset.RecordCount + 1
End Sub
Private Sub Command4_Click()
Adodc1.Recordset.Update
MsgBox "Record Updated.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command5_Click()
Adodc1.Recordset.Delete
MsgBox "Record Deleed.", vbInformation
Adodc1.Refresh
End Sub
Private Sub DataCombo2_LostFocus()
Adodc3.Recordset.Find ("itemname='" & DataCombo2.Text & "'")
Text2.Text = Adodc3.Recordset(2)
End Sub
Private Sub Text1_LostFocus()
Text3.Text = Val(Text2.Text) * Val(Text1.Text)
End Sub
RETURN Form

Private Sub Command1_Click()

Adodc1.Recordset.Update
MsgBox "Record saved.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.addnew
Text4.Text = Adodc1.Recordset.RecordCount + 1
End Sub
Private Sub Command4_Click()
Adodc1.Recordset.Update
MsgBox "Record Updated.", vbInformation
Adodc1.Refresh
End Sub
Private Sub Command5_Click()
Adodc1.Recordset.Delete
MsgBox "Record Deleed.", vbInformation
Adodc1.Refresh
End Sub
Private Sub DataCombo2_LostFocus()
Adodc3.Recordset.Find ("itemname='" & DataCombo2.Text & "'")
Text2.Text = Adodc3.Recordset(2)
End Sub
Private Sub Text1_LostFocus()
Text3.Text = Val(Text2.Text) * Val(Text1.Text)
End Sub

REPORT Form

Private Sub Command1_Click()

Datareport1.show
End Sub

Private Sub Command2_Click()

Unload Me
End Sub

Private Sub Command3_Click()

Datareport21.show
End Sub
 CONCLUSION

Now days computerizations of existing manual system is

going on a large scale because of the versatility, speed, accuracy and
diligence it offers to its users. Computers provide practical means to
organize things systematically and economically in the organization the
use of computers for managing transactions; information processing
and preparation of reports can prove to be a blessing.
The project is discussion is an attempt to attain all the
above said objectives. Its development was mean to replace the
manual system and to achieve the goal to maximum accuracy and most
efficiently. But like every other system might process faults to its credits
and has its own limitation. Neglecting these few negations, the project
can be called a stepping stone to automate processes in organizations.
 REFRENCES

References are always needed for the development of any

System / Software development. Through the system development life
cycle, I refer the following books and manuals for related sources.

Book Name Author Name

The Complete Reference Visual Basic 6 Tata McGraw Hill

Informatics Practices Sumita Arora

Visual Programming Black Book Steven Holzner