PROJECT REPORT

ON
ADVERTISING AGENCY MANAGER
In Partial fulfillment of the
Requirement for
The award of the
BECHLOR OF COMPUTER
APPLICATION

Guided By:
Submitted By:
MR. VAIBHAV VATS
SHUBHAM GUPTA
(9264010)

S.D. COLLEGE OF MANAGEMENT

STUDIES
Muzaffarnagar (U.P.) 251001
C.C.S. UNIVERSITY, MEERUT

CONTENTS
1. Acknowledgement
2. Certificate from Head of the Department
3. Introduction
4. The Minimum hardware & software specifications
5. Feasibility Report
6. Testing and Debugging
7. Security of the System
8. System Analysis and Quality Assurance
9. Cost and Benefit analysis
10. Design Overview
11. Design Goals

12. Data Dictionary

13. Front end and Backend used
14. ER- Diagram

15. Data Flow Diagram

16. Database Design
17. Coding
18. System Evaluation and Testing
19. Conclusion
20. Bibliography

ACKNOWLEDGEMENT
I want to express our heart-felt thanks to everyone who helped us to
complete this project. We would like to thanks S.D. COLLEGE OF
MANAGEMENT STUDIES, MUZAFFARNAGAR for providing us
the opportunity to undertaken ourBCA PROJECT .
Everyone knows that efficient work is nothing but mutual coordination
between two or more people. For us it was very difficult to make a real time
project without the help of people surrounding us.
We would like to express gratitude towards Mr. SHARVAN GARG
(Head of the Department) for their logistic help. With the help of scientific
people it is very easy to complete our project under these people in the
organization.
We would like to thanks S.D. COLLEGE OF MANAGEMENT
STUDIES, MUZAFFARNAGAR for their moral support. Last but not least,
thanks to the almighty that was always with us.

SHUBHAM GUPTA
(9264010)

CERTIFICATE FROM THE HEAD OF THE EPARTMENT

It is hereby certify that the work which is being presented By
SHUBHAM GUPTA in this project entitled ADERTISING AGENCY
MANAGER in partial fulfillment of the requirement for the award of BCA
by C.C.S. UNIVERSITY, MERRUT, is an authentic record on their own.
This work was carried out under the supervision of Mr. SHARVAN GARG
(HOD OF COMPUTER APPLICATION) and has not been submitted
anywhere else for the award of any degree or certificate.

A wish him or her success for every task and project they undertaken in
future also

INTRODUCTION

Our project ADERTISING AGENCY MANAGER is a project of managing the

stock and staff information with the data. The project allows users to:(1) To make the record of stock information.
(2) To make the record of staff.
(3) To make the price information of various menu.
(4) To manage the other change password controls.
What makes our project unique is that it is not only making the records for
stock and staff only. It can manage records for various menus. Processing
of our project is very user friendly. In which at the time of working a user
dont need to maintain any manual records along with the computer
transaction.

The Minimum Hardware & Software Specification

Hardware:
1. Intel Pentium Family processor; Pentium III, 500 MHz
2. Standard PC\AT Compatible with Pentium III CPU.
3. At least 32 MB RAM addressed by MS-Windows.
4. Hard Disk having 50 MB free space.
5. Mouse, 108 Keys Keyboard compatible with PC\AT.
6. Printer (Dot Matrix)
7. Color Monitor for best performance

Software:
1. Windows-Xp or above.
2. Visual Basic 6.0
3. MS Access

Required Hardware
Computer System: Standard PC/AT compatible with Pentium 2 or
Pentium 3 CPU.
Primary Memory: CASH BOOK works within 64.0 MB if User memory
(RAM) addressed by MS-WINDOWS.
Secondary Memory: CASH BOOK will work on both Hard disk as well
as Floppy Disk along with DATA BASE but better you uses Hard Disk for
voluminous data processing. It will increase the accessibility.
Output Device: Printer necessary, output will be in the form of
Spreadsheet (Excel) Forms.
Input Device: Mouse & Keyboard compatible with PC/AT. Video
Adapters and Monitors: CASH BOOK is a colored program so better to use
a colored monitor.

Required Software
Windows xp or above
Visual Basic 6.0
MS Access

FEASIBILITY REPORT
Is it feasible to automatic the system? The three major areas to determine
the feasibility of project:
1. Technical Feasibility:
The current level of technology can support the proposed system.
The proposed software is enabling to meet all the objective of the system
and output received is more efficient. So the project is technical feasible.
2. Economic Feasibility:
The proposed system needs to get hardware and software installed. The
short-term costs are over shadowed by the long-term gains. The profit of
the business is raised as this visual drafting system helps in establishing
the better relationship between clients and also satisfies their queries and
so the cost of the development of the software and hardware is over
shadowed. Thus, project is economically feasible.
4. Operational Feasibility:
The current system faces a lot of problems that are removed in the
proposed system. The Clients of the system will be free from the burden
and a lot of confusion. The clients are themselves interested in getting the
manual system replaces by the automated one. The proposal system is
user friendly, so even a layman can use it. Thus it is operationally feasible.

TESTING AND DEBUGGING

During the System Development Our Candidate System has undergone

Rigorous testing to validate & prepare our system for final implementation.
User were involved which meant for improved communication between
user & designer group.
Up short of all this is more realistic & co-operative environment for
successful testing. During system programming as each program was
code, test data is prepared and documented to ensure that all aspects of
the program are properly tested. After the testing the data are filled for
future reference. For testing we developed a test plan with an approach to
test each with successively large once, up to the system test level.
Program testing/unit testing: When a program is tested the actual
output is compared with the expected output. It checks for two types of
error:
o Syntax Error: Violation of one or more rules of language in which

it is written.
o Logic Error: Deals with the incorrect data fields, out of range item

& invalid combination. Since system diagnostics does not detect logic
errors, the programmer has carefully traced the sequence of
instructions to abide by the logic of the system.
Functional Testing: Functions are in variable related on one another
and interacting the total system. Each function is tested to see whether it
confirms to related functions in the system. Each portion of the system is

tested against the entire module both test and live data before the entire
system test was conducted.
System Testing: I included forced system failure and validation of the
total system, as its users in the operational environment will implement it. It
began with low volumes of transactions based on live data. I increased the
volume until the maximum level for each transaction type was reached.

SECURITY OF THE SYSTEM

While setting up a system aspect should be kept in mind for various
reasons like privacy of data, investment costs and levels this can be
achieved by appointing system administrator, users control supervisor etc.
this organization that depends heavily on information. These controls are
classified into:
Physical security: This security of system is performed by the protection
from fire, flood and other physical damages. For that many measures are
taken such as hardware locks, preventing access of unauthorized person
from entering the system area, keep the floppy and disk in face custody,
keeping any heat generating appliances away from the system. Obtaining
insurance cover against the risk and natural calamities.
Database integrity: to maintain the data integrity many data validation
techniques are used so that the user cannot enter any unauthorized data.
The access of database is possible only to responsible user through
password.

 Operating system level security: The measures are taken by giving no

permission to the direct access to the data in primary memory or to online
files, which protect its both program and data.
Application security: The application has also given a security measures,
so that no unauthorized person can enter the application, by giving the
password at the start of the program.
Administration security: By monitoring user on regular basis.

SYSTEM ANALYSIS & QUALITY ASSURANCE

I have determined the quality of our system through following factors:
1. Correctness
2. Reliability
3. Efficiency
4. Usability
5. Maintainability
6. Testability
7. Portability
8. Accuracy
9. Error tolerance
10. Expandability
11. Communicativeness
12. Modularity

13. Understandability

COST & BENEFIT ANALYSIS

In developing cost estimates for a system, we need to consider
servable cost elements. Among them hardware, personnel, facility,
operating, & supply costs.

Hardware Cost:
Hardware cost relate to the actual purchase or lease of the computer
& peripherals Ex. Printer, disk, floppy drive, the best way to control for this
cost is to treat it as an operating cost.

Personnel Cost:
This includes staff salaries & benefits (health insurance, vocation
time, sick pay etc.) as well as pay for those involved in developing system.
Costs incurred during the development of a system are one time costs &
are labeled developmental costs. Once the system is installed the costs of
operating &maintaining the system become recurring costs.

Facility Costs:
Facility costs are expenses incurred in the preparation of the physical
site where the application or the computer will be i operation. This includes
wiring, flooring, acoustics, lighting & air conditioning. These costs are
treated as one time costs.

Operating Cost:
Operating costs include all costs associated with the day-to-day
operating system. The amount depends on the number of sifts the nature of
the application & the calibers of the operating staff. There are various ways
of covering operating costs to overhead. Another approach is to change
each authorized user for the amount of processing they request from the
system. The amount charged is based on the computer time, staff time &
the volume of output produced.

Supply Cost:
These costs are variable costs that increase with increased use of
paper, ribbon, disks & the like they should be estimated & include in the
overall cost of the system Include rental & annual deprecation of any
equipment such as typewriter, copies, computer terminals &
microcomputers used in connection with costs associated with the
equipment, such as insurance & maintenance should also be included.

Equipment Cost:
Equipment cost include rental & annual deprecation of any equipment
such as typewriter, copies, computer terminals & microcomputers used in
connection with costs associated with the equipment, such as insurance &
maintenance should also be included.

DESIGN OVERVIEW
The design stages takes the final specification of the system from the
analysis stages and finds the best way of fulfilling them, given the technical
environment and previous decision on required level of automation

The system design is carried out in two phases

1. Architectural Design
2. Detailed Design

ARCHITECTURAL DESIGN
The high-level design maps the business system described in the program
requirement specification to logical data structure, it involves:

Identification of the entities that constitutes the system

All the entities related to the module were identified, checked and
consolidated

Identifying the Relationships

The relationships between the entities, within and outside the system were
identified.

Attribute definition
The pertaining of the entities was identified and their field characteristics
were specified.

Normalization
The entities were normalization, after first and the second normalization
was achieved for all the entities.

Interface
Interface with the other systems were done and attributes related to
external entities identified.

DETAILED DESIGN
The low level design maps the logical model of the system to a physical
database design.

Table Mapping
The Table was created for the system using the design view,
which is the part of the MS_ACCESS. This has provision to create
the entities and attributes into the Tables. The name of the entity
is taken as the table name.
Default Database Design
In Access we can create the tables very easily. The tables divide into two
parts. These names are as follow: 1. Rows
2. Columns

The steps involved here were

Generation of table
Check Validation Rule
Check Validation Text
Primary Keys
Unique Keys
Foreign Keys

Relationship
Ms-Access allows many types of relationship between the tables. These
relationship names are as follow: One to One Relationship
Many to One Relationship
Many to Many Relationships

DESIGN GOALS
Following goals were kept in mind while designing the new system
Another objective is to reduce the manual work required to be done in the
existing system, thereby avoiding errors inherent in the manual work and
hence making the outcome consistent and correct.
The important objective of the system is to provide good and reliable
information services to the top management, to take major decision which
plays a key role in the growth of any business concern. As a patient comes,
this is well understood and foreseen right from the beginning of the design
o he implementation phase of the system.
Due to the fast changes in technology, the computing speed of the machine
has grown very high, also the number of man-hour spent on the mundane
jobs in the hospital can be drastically it Menu-Drive. This in turn helps the
very first used who is unaware of the system to use it with ease.
The next objective is that it should be able to interact with the other
systems. There are many patients in all over the India or World, so it must
be possible to exchange information between different department and any
other services in the hospital. This gives the way for having an close
system which is the plug and play technique. This makes system more
effective in understanding information which is easy to handle. This makes
the system compatibly and easy to integrate into any other system. With a
view of future

DATA DICTIONARY
Data dictionary is a structured repository of data about data.
It is a list of terms and their definitions for all data items and
data stores of a system.
The primary advantages that a data dictionary offers are as
follows
1. Documentation is one of the most obvious advantages of data
dictionary. It is a valuable reference in any organization
2. It improves analysis/user communication by establishing consistence
definitions of various elements, terms and procedures.
3. During implementation it serves as a common base against which
programmers compare their data descriptions
4. Programs that use a given data elements are cross-referenced in the
data dictionary, which makes it easy to identify them and make any
necessary changes
5. A data dictionary is an important step in building a data base. Most data
base management systems have a data dictionary as a standard feature

FRONT END & BACK END USED

WINDOW XP used as PLATFORM
Windows XP is latest version of windows and also GUI. This is best
then another Operating system and easy.
Windows XP has come up with another bonanza, that is, Network
Communication with other users. The users can connect with other users to
share data files and peripheral devices, like Printers.
The Communication tools of Windows XP include E-Mail and
connection to Internet.

VISUAL BASIC used as FRONT END

Visual Basic uses front-end programming because VB use Back end
as like MS-ACCESS, ORACLE, FOXPRO and any other Database.
In VB we can use easy database connectivity and design the Form, Report,
and others MDI applications with the help of Database.
VB facility the database controls which helps the changing, modifying,
deleting and adding facility in database with the help of command buttons
and controls.
VB is used for see the Data in many modes such as with the help of
MSFlexiGrid Controls, Textbox, Combo box, List box, Image, Picture
control and other.
Visual Basic is complete programming language that supports
programming constructs for looping, decision making and efficient
processing. These constructs include
For.next
Do.loop
Selectcase
Withend with
If.then.else

Visual Basic helps of creation Menus, Master-Details Form.

Visual Basic is primarily a visual design environment .We create a Visual
Basic application by designing the forms that make up the user interface,
adding VBA code to the form and the objects such as buttons and text
boxes on them, and adding any required support code in additional
modules. Visual Basic did not bypass any version number as it progressed
toward its current release), Visual Basic continues to grow in richness and
depth faster then the Windows operating system family. With few
exceptions, virtually every type of applications can be written in Visual
Basic and probably has been.
Visual Basic applications are event-driven. Event-driven means the user is
in control of the application. The user generate a stream of events each
time he or she clicks with the mouse or presses a key on the keyboard

MS-Access used as BACK END

Ms-Access is a database and partially RDBMS. In Access we can easily
create Database design and give the validations. Access allows the many
types of relations between the tables.
Access used as Backend with the Visual Basic. Access allows creating the
Primary Key, Foreign Key and Unique Key. In Access we can store the data
in to the table for using the wizard options.
The table design window is another place you can create new tables with
Access .It is a completely different kind of tool than the Table Wizard.
Instead of choosing fields from a predefined list, you enter whatever fields
you like and select the data types for each fields.
The table design window is also the place where you add properties like
default values, input masks, and lookups to fields.
When we open a table in access, we see our data arranged in rows
and columns. This is called Datasheet view. Access has a neat feature that
lets we enter data directly into an empty datasheet view window to create a
new table .You can bypass the Database wizard, the table Wizard, and
even the table Design view window. When you create a able this way
Access takes a look at the data you enter in the various columns of the
Datasheet view window, and then makes its best guess as to what types of
field the new table should have.

DETAILED ENTITY RELATIONSHIP DIAGRAM

Identification of all the Entities of importance for which data need to be
stored and defined their relationship with each other was a major task at
this level. All the identified entities were mapped on an E-R-diagram. It is
of utmost importance to cover all the necessary entities and defined their
relationship with each other correctly because any errors at this stage
would result in the reworking in the further stages.

Date
Current balance
Particul
ar

Amount

Balance

H
as

Cb
Date

Payment

H
as

Receive

Particular

Amount
Current balance

Payment/
Receive

Transaction

Report

CB

Login name

Validation check

CB

Payment
&Receive
records

Password

Login

LOGIN
UID

MOHIT

PASSWOR
D
MITTAL

PAYMENT

PAYMENT
DATED

PARTICULAR AMOUNT

CURRENT
BALANCE

04-02-2012 ROHIT

5050

49961

05-05-2011MJ

5000

-57661

20000

62661

05-05-2012 RAM

RECEIVE
RECEIVE
DATED

PARTICULAR AMOUNT CURRENTBALANCE

04-01-2012 MOHIT

5000

55011

04-02-2012 RAM

2100

52061

05-05-2012 MOHIT

5600

57661

05-05-2012 MR

5000

-52661

25-05-2012 RAMESH

25000

82661

09-08-2012 MOHIT

25000

87661

BALANCE
BALANCE
ID OPENING
1

100000

CLOSING
87661

Dim n As Integer
Private Sub Form_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
frmlogin.Show
End If
End Sub
Private Sub Form_Load()
Me.BackColor = RGB (0, 110, 125)
Label1.Visible = False
Label2.Visible = False
Label3.Visible = False
End Sub
Private Sub Timer1_Timer ()
probar.Value = probar.Value + 1
If probar.Value = 30 Then
Me.Visible = False
frmlogin.Visible = True
Timer1.Enabled = False
End If
End Sub
Private Sub Timer2_Timer ()
n=n+1
If n = 1 Then
Label1.Visible = True
Label2.Visible = False
Label3.Visible = False
ElseIf n = 2 Then
Label1.Visible = False
Label2.Visible = True
Label3.Visible = False
ElseIf n = 3 Then

Label1.Visible = False
Label2.Visible = False
Label3.Visible = True
n=0
End If
End Sub

Private Sub cmdexit_Click ()

End
End Sub
Private Sub cmdlogin_Click ()
Set RS = New ADODB.Recordset
RS.Open "select * from login ", CON, adOpenDynamic,
adLockOptimistic, adCmdText
If RS!uid = UCase (txtuid.Text) And RS!Password =
UCase(txtpass.Text) Then
Me.Visible = False
mainform.Visible = True
Else
MsgBox "Incorrect User name and Password"
End If
End Sub
Private Sub cmdlogin_KeyPress (KeyAscii As Integer)
If KeyAscii = 13 Then
cmdexit.SetFocus
End If
End Sub
Private Sub Form_Load ()
Me.BackColor = RGB (0, 110, 125)
Call CONNECT
End Sub
Private Sub txtpass_KeyPress (KeyAscii As Integer)
If KeyAscii = 13 Then
cmdlogin.SetFocus
End If
End Sub

Private Sub txtuid_KeyPress (KeyAscii As Integer)

If KeyAscii = 13 Then
txtpass.SetFocus
End If
End Sub

Private Sub balancepermonth_Click ()

Me.Visible = False
frmbalancepermonth.Visible = True
End Sub
Private Sub cascade_Click()
Me. Arrange vbCascade
End Sub
Private Sub change_Click ()
Me.Visible = False
frmchangepassword.Visible = True
End Sub
Private Sub dispayment_Click ()
Me.Visible = False
frmdisplaypayment.Visible = True
End Sub
Private Sub disreceive_Click()
Me.Visible = False
frmdisplayreceive.Visible = True
End Sub
Private Sub htiles_Click()
Me.Arrange vbTileHorizontal
End Sub
Private Sub MDIForm_Load()
Me.BackColor = RGB(0, 110, 125)
End Sub
Private Sub tran_Click()
Me.Visible = False
frmtransaction.Visible = True

End Sub
Private Sub vtiles_Click()
Me.Arrange vbTileVertical
End Sub
Private Sub yes_Click()
End
End Sub

Private Sub CMDADD_Click()

CMDADD.Enabled = False
If txtparticular.Text = "" Or txtamount.Text = "" Then
MsgBox "PLEAS INPUT DATA"
Else
If Option1.Value = True Then
todate.AddItem txtdate.Value
toparticular.AddItem "TO " + UCase(txtparticular.Text)
toamount.AddItem txtamount.Text
On Error Resume Next
RECEIVE.AddNew
RECEIVE!DATED = txtdate.Value
RECEIVE!PARTICULAR = txtparticular.Text
RECEIVE!AMOUNT = txtamount.Text
RECEIVE!CURRENTBALANCE = BALANCE!
CLOSING
RECEIVE!CURRENTBALANCE = RECEIVE!
CURRENTBALANCE + (txtamount.Text)
BALANCE!CLOSING = RECEIVE!
CURRENTBALANCE
BALANCE.Update
RECEIVE.Update
MsgBox "SUCCESSFULLY SAVED"
Else
bydate.AddItem txtdate.Value
byparticular.AddItem "BY " + UCase(txtparticular.Text)
byamount.AddItem txtamount.Text
On Error Resume Next
PAYMENT.AddNew
PAYMENT!DATED = txtdate.Value
PAYMENT!PARTICULAR = txtparticular.Text
PAYMENT!AMOUNT = txtamount.Text
PAYMENT!CURRENTBALANCE = BALANCE!
CLOSING

PAYMENT!CURRENTBALANCE = PAYMENT!
CURRENTBALANCE - (txtamount.Text)
BALANCE!CLOSING = PAYMENT!
CURRENTBALANCE
BALANCE.Update
PAYMENT.Update
MsgBox "SUCCESSFULLY SAVED"
End If
End If
End Sub
Private Sub CMDADD_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
cmdexit.SetFocus
End If
End Sub
Private Sub cmdexit_Click()
Me.Hide
mainform.Show
End Sub
Private Sub cmdnext_Click()
CMDADD.Enabled = True
txtparticular.Text = ""
txtamount.Text = ""
Option1.SetFocus
End Sub
Private Sub Form_Load()
Me.BackColor = RGB(0, 110, 125)
Call CONNECT
RECEIVE.Open "SELECT * FROM RECEIVE", CON,
adOpenDynamic, adLockOptimistic

PAYMENT.Open "SELECT * FROM PAYMENT", CON,

adOpenDynamic, adLockOptimistic
BALANCE.Open "SELECT * FROM BALANCE", CON,
adOpenDynamic, adLockOptimistic
B = BALANCE!CLOSING
If Left(B, 1) = "-" Then
bydate.AddItem Date
byparticular.AddItem "TO BALANCE C/D"
byamount.AddItem BALANCE!CLOSING
Else
todate.AddItem Date
toparticular.AddItem "TO BALANCE B/D"
toamount.AddItem BALANCE!CLOSING
End If
End Sub
Private Sub Option1_Click()
txtparticular.SetFocus
End Sub
Private Sub Option2_Click()
txtparticular.SetFocus
End Sub
Private Sub txtamount_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
CMDADD.SetFocus
End If
End Sub
Private Sub txtdate_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
txtparticular.SetFocus
End If
End Sub

Private Sub txtparticular_KeyPress(KeyAscii As Integer)

If KeyAscii = 13 Then
txtamount.SetFocus
End If
End Sub

Private Sub CMDBACK_Click()

Me.Hide
mainform.Show
End Sub
Private Sub cmdpayment_Click()
Set paymentgrid.DataSource = PAYMENT
cmdprint.Enabled = True
End Sub
Private Sub cmdprint_Click()
DRpayment.Show
End Sub
Private Sub Form_Load()
Me.BackColor = RGB(0, 110, 125)
cmdprint.Enabled = False
Call CONNECT
PAYMENT.Open
selectDATED,PARTICULAR,AMOUNT,CURRENTBALANCE
FROM PAYMENT ", CON, adOpenDynamic, adLockOptimistic,
adCmdText
End Sub

Private Sub CMDBACK_Click()

Me.Hide
mainform.Show
End Sub
Private Sub cmdprint_Click()
DRreceive.Show
End Sub
Private Sub cmdreceive_Click()
Set receivegrid.DataSource = RECEIVE
cmdprint.Enabled = True
End Sub
Private Sub Form_Load()
Me.BackColor = RGB(0, 110, 125)
cmdprint.Enabled = False
Call CONNECT
RECEIVE.Open "select
DATED,PARTICULAR,AMOUNT,CURRENTBALANCE FROM
RECEIVE", CON, adOpenDynamic, adLockOptimistic
End Sub

Private Sub cmbmonth_KeyPress(KeyAscii As Integer)

If KeyAscii = 13 Then
cmbnature.SetFocus
End If
End Sub
Private Sub cmbnature_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
cmdok.SetFocus
End If
End Sub
Private Sub CMDBACK_Click()
Me.Hide
mainform.Show
End Sub
Private Sub cmdok_Click()
Set RS = New ADODB.Recordset
Dim m As Integer
m = Val(cmbmonth.Text)
If cmbnature.Text = "Payment" Then
RS.Open "select * from PAYMENT where Month(DATED)=" +
Str(m), CON, adOpenDynamic, adLockOptimistic, adCmdText
Set balpermonth.DataSource = RS
ElseIf cmbnature.Text = "Receive" Then
RS.Open "select * from RECEIVE where Month(DATED)=" +
Str(m), CON, adOpenDynamic, adLockOptimistic, adCmdText
Set balpermonth.DataSource = RS
End If
End Sub
Private Sub Form_Load()
Me.BackColor = RGB(0, 110, 125)
Call CONNECT
End Sub

Private Sub cmdchange_Click()

LOGIN.AddNew
LOGIN!uid = UCase(txtnewname.Text)
LOGIN!Password = UCase(txtnewpass.Text)
LOGIN.Update
LOGIN.Close
MsgBox "SUCCESSFULLY CHANGE"
txtoldname.Text = ""
txtoldpass.Text = ""
txtnewname.Text = ""
txtnewpass.Text = ""
End Sub
Private Sub cmdchange_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
cmdexit.SetFocus
End If
End Sub
Private Sub cmdexit_Click()
Me.Visible = False
mainform.Visible = True
End Sub
Private Sub cmdverify_Click()
If LOGIN!uid = UCase(txtoldname.Text) And LOGIN!Password
= UCase(txtoldpass.Text) Then
MsgBox "Verify"
LOGIN.Delete
LOGIN.Update
txtnewname.SetFocus
Else
MsgBox "Not Verified. TRY AGAIN", vbYesNo
txtoldname.Text = ""
txtoldpass.Text = ""

txtoldname.SetFocus
End If
End Sub
Private Sub cmdverify_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
txtnewname.SetFocus
End If
End Sub
Private Sub Form_Load()
Me.BackColor = RGB(0, 110, 125)
Call CONNECT
LOGIN.Open "LOGIN ", CON, adOpenDynamic,
adLockOptimistic
End Sub
Private Sub txtnewname_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
txtnewpass.SetFocus
End If
End Sub
Private Sub txtnewpass_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
cmdchange.SetFocus
End If
End Sub
Private Sub txtoldname_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
txtoldpass.SetFocus
End If
End Sub
Private Sub txtoldpass_KeyPress(KeyAscii As Integer)

If KeyAscii = 13 Then
cmdverify.SetFocus
End If
End Sub

MODULE
Public CON As Connection
Public RECEIVE As Recordset
Public PAYMENT As Recordset
Public BALANCE As Recordset
Public LOGIN As Recordset
Public RS As Recordset
Public Sub CONNECT()
Set CON = New Connection
Set RECEIVE = New Recordset
Set PAYMENT = New Recordset
Set BALANCE = New Recordset
Set LOGIN = New Recordset
With CON
.ConnectionString = "DSN=CASHBOOK"
.ConnectionTimeout = 3
End With
CON.Open
End Sub

SYSTEM EVALUATION AND TESTING

During system testing, the system is used experimentally to
ensure that the software does not fall, i.e. it will run according to
specification and in the way users expect. Special test data input
for processing and the result examination. A limited number of
users may be allowed to use the system so that analysis can see
whether they use it in unforeseen ways. It is preferable to
discover any surprises the organization implements the system
and encounters them later on. This type of testing which allows
only a few, selected users to work on the system is known as
BETA TESTING. On the other hand the testing done by the
developer (s), themselves is known as ALPHA TESTING.
Testing is generally performed by persons other than those
who the original programs to ensure complete and unbiased
testing and more reliable software
The norms followed during the testing phase were
thoroughly tested by me, the developer; I was required to release
the programs source code. The source code was copied into the
area. If some changes were desired in the program, I was suitably
informed and was required to make the necessary modifications.
Following testing procedures were used
UNIT TESTING

Unit testing is the testing of a single program module in an

isolated environment. The testing of the processing procedure is
the main focus. In this regard, all the modules were separately
tested first as isolated and complete entities. This helped a lot in
discovering problems related to a single module and rectifying
them in the contest of the module itself, rather than considering
module-related problem in a global context
INTEGRATION TESTING
Integration testing is the process of testing the interfaces
among system modules. Some testing ensures that data moves
between systems as intended. In the regard of a particular
module was obtained in correct format, so that the next module
could accept it appropriately. This could be done either after the
entire system was developed, or in stages than one module was
developed.
SYSTEM TESTING
System testing is the testing of the system against its initial
objectives. Such testing is done either in a simulated environment
or in a live environment.
In the case of the system which I developed, the testing was
done in a pseudo-real environment. The organization has an area
called the Development , where all development work is carried

out, whereas the Client is the area where all on-line work is
undertaken. Since the kind of work which I was involved dealt with
insertion, updating and in tables, all the work was developed in
the Development area. I call the environment pseudo-real since
all data which is being used for on-line transaction can be copied
into the tables of the Development and live data can be worked
on. Thus whatever would be the output on the Client is reflected
exactly on the Development also? Thus, discovery of error
became simpler in that the errors which would occur in the realtime environment were exactly duplicated in the Development
environment.
All the above types of testing were carried out and various
extreme cases were also introduced to check for whether the
system responded as expected. The various Forms, database
packages, procedures, function; visual basic programs and
functions were tested to discover they behaved in the manner
expected of them and gave accurate results. However, the factor,
which helped most in the modification and rectification of the
system, was the user response. The user after using the system
would invariably come up with some idea to improve the system.
Such ideas, if feasible, were incorporated into the system, thus
leading to an improvement in the overall efficiency of the system.

SYSTEM IMPLEMENTATION
Implementation, literally, means to put into effect or to carry
out. The system implementation phase of software engineering
deals with all activities that take place to convert from the old
system to the new. Proper implementation is essential to provide
system to meet organizations requirements.

During the implementation phase debugging, documentation

of the system was created out, module in the project for
Accuracy of Results,
Minimization of response Time,
Clarity and Simplicity of the code,
Minimization of Hard Coding i.e. (a generic approach was
followed)
Minimization of amount of memory used.
Various types of errors were discovered while debugging the
modules. These ranged from errors to failure to account for
various processing cases. Proper documentation of each module
was done by embedding comments in the executable portion of
the code. To enhance the readability, comments, indentation,
parenthesis, black spaces, blank lines and borders were around
the blocks of comments. Care was taken to use descriptive
names for table, field, modules, forms etc., the proper use of
indentation, parenthesis and blank lines was also ensured during
coding.
Testing of the Report Generation module was carried out to
find out the response time of the system for the generating
reports. To make the response time negligible.

SYSTEM MAINTENANCE
Maintenance is a fact of life in the development of information
systems. However the making of changes & adjustments dont
necessarily signal correction of error or the occurrence of
problems.
Among the most frequent changes requested by end users
is the addition of information to a report format. Information
requirements may be revised as the result of system usage or

changing operational needs. Perhaps oversights that occurred

during the development process need to be corrected.
Often, the need arises to capture additional data for storage
in a database or perhaps when it is necessary to add error
detection features to prevent system users from inadvertently
taking an unwanted action.
These are the realities of application maintenance, when
they occur, however they are an indication that the system is
being used & that it is serving a useful function rather than being
shelved by the intended, such as :
More accurately defining the users requirements during system
development.
Assembling better systems documentation.
Making better use of existing tools & techniques.
Including proper comments.

SYSTEM DOCUMENTATION
Documentation is the process of collecting, organizing,
storing and maintaining on paper (or some relatively
permanently medium) a complete record of why application
were developed, for whom, what function they perform, and
how these functions are carried out. Thus it provides an
explanation of how a system operates & what feature characterize
models & algorithms. Producing documentation is an important
but often neglected activity of programmers.
Documentation of the system always reduces maintenance
costs and makes maintenance much easier. Documentation can
be broadly classified as:

 INTERNAL DOCUMENTATION
EXTERNAL DOCUMENTATION
INTERNAL DOCUMENTATION
Internal documentation in the code can be extremely useful
in enhancing the understandability of programs. Internal
documentation of programs is done by the use of comments. All
the languages provide means of writing comments in the
programs. Comments are textual statements that are meant for
the reader and are not executed. Comments, if properly written,
and if kept consistent with the code, can be invaluable during
maintenance.
The purpose of comments is not to explain the internal logic
of the program the program itself is the best documentation for
the details of logic. The comments should explain what the code
is done is doing, and not how it is done it.
Comments should be provided for the block of code,
particularly those parts of code which are hard to follow.
Providing comments for module is most useful as module
form the unit testing, compiling, verification and modification.
Comments for a module are often called prologue for the module.
It is best to standardize the structure of the prologue of the
module. It is desirable that prologue contains the following
information:
Module functionality or what the module is doing
Parameters are their purpose
Assumptions about the input, if any
Global variable accessed and or modified in the module

As explanation of parameters (whether they are input only, output

only or both input and output, why they are needed by the module
and how the parameters are modified) can be quite useful during
maintenance.
In addition to that given above, often information can be
included, depending on the local coding standards. Example
includes:
Name of the author,
Date of compilation
Last date of modification.
Note that if the module is modified, then the prologue should also
be modified, if necessary. A prologue that is inconsistent with the
internal logic of the module is prologue worse than having no
prologue at all.
While coding programs for the Station Coding System special
attention has been paid to the internal documentation of the
system, in addition to the external documentation. Each
program/module has:
Program/module name on top
Date of creation of the program
Last modification date
The S/W tool used to developed the program
Description of input to the program/module
Description of the output produced
How the module is related to other modules
Purpose of variables/constants used
Apart from this comment lines have been inserted
wherever it was felt that they were necessary. Moreover

meaningful variable names/constants have been assigned

to different variable/constants used in the programs.

EXTERNAL DOCUMENTATION
The external documentation of the system contains all the
relevant information about the system which is not included within
the programs. The external documentation typically explains:
What is the basic purpose of the system?
Why the system was developed?
The platform on which the system will run.
The various trouble shooting mechanisms.
The operations guide.

CONCLUSION
The project made me realize the significance of developing
software for client, where all the eventualities have to be taken
care of, unlike at different organization, where the sole aim is to
keep track of employees. What may be seen to the developed to
be software complete in all respects, I was required to meet the
stringent demands of the in-house client in the materials
department. Through this seemed tough at first, I realized that
pressure goaded us on to develop better and better applications.
During the project, the real importance for following all the
principle of System Analysis and Design drawled on me. I felt
the necessity of going through the several stages, because only
such a process could make one understand the problems at
hand, more so due to the enormous size of data stores involved
and their manipulation

In retrospect, I would like to say that the institute provided us

with many opportunities to learn Oracle 8i and its tools. I
specifically was able to learn MS-ACCESS and its Tools. I
specially was able to learn VISUAL BASIC 6.0. I also succeeded
in understanding a number of tricky concept in database, which
were earlier only hazy blobs in the realm of our comprehension. I
hope this stint at payroll would stand me in good stead in future
endeavors.
However my project CASH BOOK is an asset to the organization,
even then
FURTHER ENHANCEMENT is possible in this project such as
new forms & reports can be included as and when required.
Unfortunately due to lack of time we can developed any report in
this system but this is not the end of this system software, it is
beginning. We can change and modify this software due to more
requirements of needs and also removed some errors which is
finding in this system software.
We also developed some complex reports which is required and
makes this software more powerful and friendly for user by which
user can handle library data more easily and can calculate all the
calculation without any other software i.e., users all the
requirements will be fulfill by this software and user can manage
all the numeric data calculations.

LIMITATION
Limitation about the Software about we can say as in
development in Visual Basic as size increase searching as speed
will be show in compare dos.

SCOPE FOR FUTURE

It will be save money according to its performance also will be
helpful fast accessing of the organization.

BIBLIOGRAPHY
BOOK NAME

AUTHOR

Complete Reference of MS-Office

Tec media

An Introduction to Database Systems

C. J. Date

The Complete VISUAL BASIC

Telic

Programming in VB

P.K.M Bride

Visual Basic from the Ground Up

Gary Cornell