Visual Basic 6.0 Project On Accounting System

CHAPTER-1
INTRODUCTION
1.1 Background Study:

An accounting system allows a business to keep track of all
types of financial transactions, including purchases (expenses), sales
(invoices and income), liabilities (funding, accounts payable), etc. and is
capable of generating comprehensive statistical reports that provide
management or interested parties with a clear set of data to aid in the
decision-making process.
Accounting is the language of business. It is the system of recording,

summarizing, and analyzing an economic entity's financial transactions.
Effectively communicating this information is key to the success of every
business. Those who rely on financial information include internal users,
such as a company's managers and employees, and external users, such as
banks, investors, governmental agencies, financial analysts, and labor
unions.
However, historically, accounting systems were a complex series of manual

calculations and balances.
1.1.1 The organization profile:

The main work of this organization is maintaining the records of
customer and the work of maintaining records is done on the register.
1.1.2 Study of the existing system:

The existing system was a manual one. Whatever be the process
involved in the system were done through register (files). There were lots
of complexities involved in the system. When any customer takes new
1
connections then separate files were maintained. Updating of data was
very tedious job. It was not easy to do several administrative works like
managing rates of properties , addition or modification of property details
& customer entries.
1.2 Project overview:

The project is highly flexible and is well efficient for
managing all information about the Buyer And Seller of property. The key
focus is: well management of data and easy retrieval of information. The
speed and accuracy should be maintained in a proper way. Changes can
be done very easily using the facility and flexibility in v.b. 6.0 and access
2007. The software can be developed in a neat and simple manner hence
it reduces operator’s work.
1.3 Objective of the project:

The main goal of this project is to make the record of
customer’s easier & quicker.
 It is situated for all level of peoples.

 It provides proper details about all the customer & their records.
 User friendly environment makes the data handling more easily.
 It easily provides an environment where the user can get information
about all the customers & there records.
2
CHAPTER-2
PROBLEM ANALYSIS
2.1 Study of the proposed system:
The organization would be headed by the proprietor, who
responsible for authorization functions and for the approval of the
purchase requisition and disbursing functions.
The manager’s functions would be the one in-charge in depositing
the cash received from sales to the bank, receiving inventories, and
preparing some necessary documents.
The accountant is in-charge of journalizing and posting of
transactions. Also, he is responsible in preparing the financial statements of
the company.
This software helps you to track all the profits, loss, profitable
clients and products of accounting software moreover it’s a accounting
software. Flexible and adaptive software suited to accounting system.
This System will store the information of accounts in the system. It
will also store the information about stock details. This system provides
security by granting access rights for changing the sensitive data to
administrator only. Customized search options are also available in this
system. This system can generate all kinds of reports as per the user’s
requirements.
Important features of this proposed system are:

 Consistent user interface with high economic features built into it.
 System design in modular and structured way so as to make the
integration with other subsystems easier.
3
 User has complete control as it provides and accept only appropriate
and valid data.
 User-friendly error messages are provided wherever necessary.
 Addition, deletion, modification of records as when needed.
 Providing connections to new customers.
 Bill generation for customers.
OBJECTIVES OF THE PROPOSED SYSTEM
 To reduce workload of staff.

 To reduce the delay in processing time.
 To reduce the delay in bill generation.
 To provide the user-friendliness in all possible ways.
 To provide greater flexibility.
 Make maintenance changes easy.
 To store data in a centralized location to reduce redundancy and
increase consistency.
2.1.1 Problem definition:

In the old system the main task of editing is not done
easily & it will also take time. Such as:
 Data can easily be misuse, if the safety is not taken.
 It is very time consuming process.
 User cannot keep the records or information of full data
accurately.
 It is not reliable to keep the records in the registers.
But in the proposed system the main assumptions are, the
system should already contains all the hardware’s & software’s as well as
the person who use this product should familiar with win 98 or win xp or
any operating system.
4
2.1.2 Solution strategies:
The main solution of the problem is to provide suitable &
user friendly environment to a user so that the user can maintain the
detail of customer in a very easy manner.
2.2 SYSTEM REQUIREMENT:

Hardware Requirement
The configuration given below is the Hardware handled for the system
development.
Processor : PENTIUM III or Above
Primary Memory (RAM) : 64 MB or Above
Secondary Memory (Hard disk) : 20 GB or Above
Monitor : COLOR, 10 inch or above
Display card : SVGA
Mouse : Any Company
Cabinet : Any Company
Software Requirement
Operating System : Windows 98 or above
Front End tool : Visual Basic 6.0
Back End tool : MS-Access
2.3 SOFTWARE JUSTIFICATION:

Operating System
As the Shop is presently has its situated in One place, STAND ALONE system is
proposed with WINDOWS 98 operating system.
5
Front End tool
Visual Basic 6.0
Microsoft Visual Basic 6.0 is the powerful programming language to develop

application for windows. Windows is the operating system, which runs based on
messages and with rich user interface. Here are little details about how windows
works and programming model using Visual Basic.
MICROSOFT VISUAL BASIC 6.0
Visual Basic 6.0 is an enjoyable language due to its visual environment.

Building a windows program in Visual Basic requires dragging and dropping
graphic objects on to the screen from a toolbox. Thus Visual Basic is the efficient
GUI tools to develop some exciting windows-based application.
Visual Basic 6.0 is much more than just a programming language. The
programming language forms the background of all that takes place in a running
Visual Basic program. The language is a secondary consideration to the user
interface. A windows program offers a high degree of user interaction using the
graphical elements that forms the objects on the window the user sees .If the
user interface is not correct, user will not like the program.
Visual Basic lets one add menus, text boxes, command buttons, option buttons
(for making exclusive choice), check boxes, list boxes, scroll bars and file and
directory boxes to black windows. One can use Visual Basic to communicate with
other applications, running under windows. Visual Basic offers: More Internet
features, better support for data base development, more language feature to
make programming job easier.
6
SOME TOOLS OF VISUAL BASIC 6.0
 Data access features allow creating databases, front-end applications and
scalable server side components for most popular databases formats
including Microsoft SQL server and other enterprise level databases.
 Active X technology allows using functionality provided by other
applications such as Microsoft Word, Microsoft Excel and other applications
and objects could be created using the Professional Enterprise editions of
Visual Basic.
 Internet capabilities make it easy to provide access to documents and
applications across the Internet or Intranet server applications.
The finished applications are a true .exe files that uses a Visual Basic virtual
machine that can be freely distributed.
SIGNIFICANCE FEATURES OF VISUAL BASIC 6.0
Toolbox: The Tool Box window differs from the tool bar. The Tool Box is a
collection of tool that acts as a repository of controls we can place on forms.
Some tools are Selection Pointer, Picture Box, Label, Text Box, Frame Button,
Command Botany, Check Box, Option Button etc.
Form: Visual Basic uses a window; controls are the widgets one place of a form.
In a form we will customize by adding controls such as command buttons, list
boxes to it. At the top of the black form is the little bar with its caption.
Common Form properties:
There are several common properties to customize a form, these are: -
Caption: Caption is used as a title that the Microsoft Window for the application
icon when the user minimizes the application.
Name: This property is used to give the name that one want to use to refer to the
form.
7
Enabled: If user sets Enabled to false, the form cannot respond to any events
such as the user checking on the form.
Icon: The icon property determines the icon users application will display when it
is minimized on tool bar or turned into a stand-alone application on windows
desktop.
Visible: If the value of the property is set to false, it will no longer be visible.
Text Boxes:
It is used to display text or to accept user input. Most of the code is written to
process the information users enter into them. Several properties of text boxes
are as follows: -
Text: The text property in text box is the analog of the caption property for a
command button or a form; it controls text the users see. It determines whether
text on the control such as label or command button, is left justified, centered, or
right justified on the control. The Alignment property take one of the three
values: 0-Left justify, 1-Right justify, 2-Center.
Multiline: This property determines whether a text box can accept more than one
line of text when the user runs the application, and it is usually combine with
resulting the value of the scrollbar property. If true the property specifies the text
box can hold more than a line of text.
Max Length: This property specifies the maximum number of characters that the
text box will accept. A value of 0 indicates that the user can enter a value of any
length.
Locked: This property determines whether the user can enter a value or change
the default value of the text box. If true, the user cannot change the text box
value until the program, at run time assigns a false to this property.
Password char: The Password property lets us limit what the text box displays.
8
Labels: Use Labels to display information programmer does not want the user to
be able to change. Most common use for Labels is to identify a text box or other
control by describing its contents. Another common use is to display help
information.
Message Boxes:
Message boxes display information in the dialog box superimposed on the
form. They want for the user to choose a button before return to the
application. User cannot switch to another form in programmers applications
as long as Visual Basic is displaying a message box.
Value Named constant Description

0 vbOKOnly OK button
1 vbOKCancel OK and Cancel buttons
2 vbAboRetryIgnore Abort,Retry and Cancel buttons
3 vbYesNoCancel Yes and No and Cancel buttons
4 vbYesNo Yes and No buttons
MsgBox “ The message goes in codes”, 4
Frames:
Programmer usually frames passively to group images or controls.
Option Buttons:
They all work together. When the user chooses one button, all other buttons in
the group are turned off. The value property of the option button tells us whether
9
a button was selected by the user. If the value property is true, the user selected
that button; otherwise, its value property is false.
Check Boxes:
Check Boxes differ from option button in that, regardless of how many Check
Boxes one places on a form, they can all be turned on and off independently. If
the user has selected Check Boxes, the value property switches to true. It stays
true until the user deselects that box.
List and Combo boxes:
Use list boxes when we have a fixed list of choices. Visual Basic automatically adds
vertical scroll bars when the list box is small for all items it contains.
To allow users to input data as well as choices from a list, we use a Combo Box.
FOLLOWING ARE THE CUSTOM CONTROLS, WHICH ARE

ALSO DATA AWARE:
 Data List
 Data Combo
 Data Grid
 Microsoft Flex Grid
 Microsoft Hierarchical Flex Grid
 Rich Textbox
 Microsoft Chart
 Date Time Picker
 Image Combo
10
How Windows Works
WINDOWS, EVENTS AND MESSAGES
Windows involves three key concepts: windows, events and messages.
Think of a window as a rectangular region with its own boundaries. For example,
Explorer window in Windows, a Document window within word processing
program, or a dialog box that pops up to remind you of an appointment. A
command button is also a window. Icons, text boxes, option buttons and menu
are all windows.
The Microsoft Windows operating system manages all of these many windows by
assigning each one a unique id number (window handle or hewn). The system
continually monitors each of these windows for signs of activity or events. Events
can occur through user actions such as a mouse click or a key press, through
programmatic control, or even as a result of another window’s actions.
Each time an event occurs, it causes a message to be sent to the operating
system. The system processes the message and broadcasts it to the other
windows. Each window can then take the appropriate action based on its own
instructions for dealing with that particular message (for example, repainting
itself when it has been uncovered by another window).
Dealing with all of the possible combinations of windows, events and messages
could be very difficult. Many of the messages are handled automatically by Visual
Basic; others are exposed as event procedures for our convenience. This allows us
to quickly create powerful applications without having to deal with unnecessary
details.
UNDERSTANDING THE EVENT-DRIVEN MODEL

In traditional or “procedural” applications, the application itself controls which
portions of code execute and in what sequence. Execution starts with the first
line of code and follows a predefined path through the application, calling
procedures as needed.
In an event-driven application, the code doesn’t follow a predetermined path – it
executes different code sections in response to events. The sequence of these
11
events determines the sequence in which the code executes, thus the path
through the application’s code differs each time the program runs.
Because we can’t predict the sequence of events, our code must make certain
assumptions about the “state of the world” when it executes. When we make
assumptions (for example, that an entry field must contain a value before running
a procedure to process that value), we should structure our application in such a
way as to make sure that the assumption will always be valid (for example,
disabling the command button that starts the procedure until the entry field
contains a value).
Our code can also trigger events during execution. For example,
programmatically changing the text in a text box cause the text box’s Change
event to execute. If you assumed that this event would only be triggered by user
information, you might see unexpected results. That’s why it is very important to
understand the event-driven model and keep it in mind when we design the
application.
INTERACTIVE DEVELOPMENT
The traditional application development process can be broken into three distinct
steps: code writing, compiling the code, and testing code. Unlike traditional
languages, Visual Basic uses an interactive approach to development, blurring the
distinction between the three steps.
With most languages, if we make a mistake in writing the code, the compiler
catches the error when we start to compile the application. We must then find
and fix the error and begin the compile cycle again, repeating the process for each
error found. Visual Basic interprets the code as we enter it, catching and
highlighting most syntax or spelling errors on the fly. It’s almost like having an
expert watching over our shoulder as we write the code.
In addition to catching errors on the fl, Visual Basic also partially compiles the
code as it is entered. When the code is ready to run and test the application,
there is only a brief delay to finish compiling. If the compiler finds an error, it is
highlighted in the code. We can fix the error and continue compiling without
having to start over.
12
Because of the interactive nature of Visual Basic, we can’t test the effects of the
code as we work rather than waiting to compile later.
USER INTERFACE ELEMENTS
Visual Basic provides us a lot of User Interface elements, which are easier to
create and use. For example Forms, Menus, dialog boxes and supporting controls
such as Check Box, List Box, Edit Box, Etc.
DATA BASE CONNECTIVITY
Visual Basic supports a lot for data base connectivity; we can use ODBC to
connect with different databases like Oracle, Sybase, Etc.
Back End Tool [MS-Access]
On a program of software that can help us to access data and perform operations
it is called a “Data Base Management System”. The DBMS whose design is based
on the Relational Theory is called “The Relational Database Management System”
or RDBMS.
MS-Access is a RDBMS, offers capabilities of both Relational and Object Oriented

database systems. It supports very large databases that could contain hundreds of
terabytes of information. The records are represented in a flat two dimensional
table with rows and columns. Each column has an unique name. All elements in
each column are of same kind.
13
MS-Access provides access to many concurrent users to the order of thousands
managing large amount of data could present administrative and performance
challenges.
MS-Access is the default backend for Visual Basic. Creating tables and making
data entries in MS-Access are made easier. It has the advantage of querying. It is
more faster in retrieving data. The data can also be external to the database. It
has enriched data types.
MICROSOFT ACCESS
Database: -A database is a set of data, organized for easy access. The database is
the actual data. It is the database that you will be accessing when you need to
retrieve data.
Data Dictionary: -The data dictionary is a set of tables Access uses to maintain
information about the database. The data dictionary contains information about
tables, indexes, clusters, and so on.
DBA (Database Administrator): -The DBA is the person responsible for the
operation, configuration, and performance of the database. The DBA is charged
with keeping the database operating smoothly, ensuring that backups are done
on a regular basis (and that the backups work), and installing new software. Other
responsibilities might include planning for future expansion and disk space needs,
creating databases and tablespaces, adding users and maintaining security, and
monitoring the database and retuning it as necessary. Large installations might
have teams of DBAs to keep the system running smoothly; alternatively, the tasks
might be segmented among the DBAs.
DBMS or RDBMS: -The Database Management System is the software and

collection of tools that manages the database. Access software is the DBMS. A
Relational Database Management System is a DBMS that is relational in nature.
14
This means that the internal workings access data in a relational manner. Access is
an RDBMS.
Query: -A query is a read-only transaction against a database. A query is

generated using the SELECT statement. Users generally distinguish between
queries and other transaction types because a query does not change the data in
the database.
Schema: -A schema is a collection of objects associated with the database.
Microsoft Access is a very effective DBMS tool which is generally used by all the
users. It is compatible with all types of systems & can be installed and used as and
when required.
2.4 COST ESTIMATION AND SCHEDULING:
Project estimation and scheduling were carried out together by the project leader
as Per the norms of the company. Some cost estimation was done at the early
stage before the schedules were drawn up. Once the project was underway,
estimates were updated. The factors involved in computing the total cost of a
software project were
* Hardware & software cost,

* Maintenance cost,
* Travel and training cost and
* Effort cost.
Scheduling as well as estimating the effort required to develop the software

system were done by the project leader in discussion with the Company officials.
15
CHAPTER-3
DESIGN & DEVELOPMENT PROCESS
3.1 Design Notations:
3.1.1 Data Flow Diagram:
Zero level Data Flow Diagram:
16
First level Data Flow Diagram:
17
3.1.2 E-R Diagram:
18
3.2 Design Process:
3.2.1 Database design:
Login Table:
Purchase Table:
19
Sales Table:
Company Table:-
20
Stock Table:-
Profit\Loss Table:-
21
Balancesheet Table:-
22
3.2.2INPUT DESIGN
Errors committed by data entry operator can be controlled by the input
design. The following approaches have been incorporated into the input
design of the proposed system.
MENU
A menu is a selection list that simplifies the data entry the user can
choose from a list of option, by typing the option letter associated with
option in position where the cursor is located.
This project has both Graphical Menu and also Pull down Menu
Graphical Menu is designed in such a way that, if the user moves the
mouse cursor above the main option – sub options displayed
automatically.
FORMATTED SCREEN
Data entry screens have been designed which are similar in formatting
source documents. Help screens have been designed the user to enter
data without confusion.
DATA VALIDATION
The input data are validated to minimize errors validation is done. In
certain cases validation is made to check whether the given data is
numeric or not.
23
USER FRIENDLINESS
Appropriate messages are provided to the user to inform of what is
happening. Errors are used to indicate the error code and specific error
message.
CONSISTENT FORMAT
A fixed format is adopted for displaying the title and the messages. Each
screen has a status line, which displays the operation that can be
performed after data entry.
INTERACTIVE DIALOGUE
The system participates in interactive dialogue and is able to cope with
missing or omitted information. It covers the dialogue by retaining
adequate information between each dialogue.
3.2.3 OUTPUT DESIGN

It is necessary that the output reports be compatible format with the
manual reports. The output has been designed in mind. Output design is
the basis by which many users evaluate the usefulness of the system. The
output forms used in this software are required for query response and
reports. The emphasis is required for producing the hard copy of the
information requested or displaying the output on a CRT screen.
24
CHAPTER-4
TESTING & IMPLEMENTATION
4.1 SYSTEM TESTING:
Software testing is a crucial element of software quality assurance and
represents the ultimate review of specification, design and coding. The increasing
visibility of software as a system element and the attendant "cost" associated
with a software failure are motivating forces for well-planned, thorough testing.
Testing is a set of activities that can be planned in advance and conducted
systematically. Testing begins at the module level and work towards the
integration of entire computers based system. Nothing is complete without
testing, as it is vital success of the system.
Unit Testing
Unit testing focuses on the verification of smallest unit of software design
of the module. To check whether each module in the software works properly so
that it gives desired outputs to the given inputs. All validations and conditions are
tested in the module level in unit test. Control paths are tested to ensure the
information properly flows into and out of the program unit under test. Boundary
condition are tested to ensure that the modules operates at boundary establishes
to restrict processing. All independent paths through control structure are
exercised to ensure that all statements in a module have been executed at least
once. And finally all errors handling paths are tested.
In our system, Unit testing has been successfully handled. The test data was
given to each module in all respects and have got desired output. Each module
has been found working properly.
Black Box Testing

Black Box Testing methods focus on the functional requirements of the
software. This testing enables the software engineer to derive sets of input
conditions that will fully exercise all functional requirements for a program. This
25
testing attempts to find errors in the following categories: incorrect or missing
functions, interface errors, errors in data structure or external database access,
performance errors and initialization errors and termination errors. In our system,
Black Box testing has been successfully handled. The test input data was given has
got desired output.
User Acceptance Testing

The performance of user interactive testing is actually the user show. The
user gives live data and checks whether software is giving specified outputs .
4.2 SYSTEM IMPLEMENTATION:
4.2.1 Implementation Procedures :
Implementation is the phase where the system goes for actual functioning.
Hence in this phase one has to be cautious because all the efforts undertaken
during the project will be fruitful only if the software is properly implemented
according to the plans made.
The implementation phase is less creative than system design. It is primarily
concerned with user training, site preparation and file conversion. Depending
on the nature of the system, extensive user training may be required. The
initial parameters of the MIS should be modified as the result of programming
efforts; programming provides a reality test for the assumptions made by the
analyst.
4.2.2 Operational Documentation:
The system testing checks the readiness and accuracy of the system to access,
update and retrieve data from new files. Once the programs become available,
the test data are read into the computer and process.
26
4.3 SYSTEM MAINTENANCE:
We may define Software Maintenance by describing four activities that are

undertaken after a program is released for use.
Corrective Maintenance
The first maintenance activity occurs since it is unreasonable to assume
that software testing will uncover all errors in a large software system. The
process of including the diagnosis and correction of one or more errors is called
corrective maintenance.
Adaptive Maintenance
This activity that contributes to the definition of maintenance occurs since
rapid change is encountered in every aspect of computing. Therefore, adaptive
maintenance modifies software to properly interface with the changing
environment.
Perfective Maintenance
This activity involves recommendations for new capabilities, modifications
to the existing functions and general enhancements when the software is used.
To satisfy these requests, perfective maintenance is performed.
Preventive Maintenance
This activity occurs when software is changed to improve further
maintainability or reliability. If the only available element of a Software
Configuration is the source code, maintenance activity begins with the evaluation
of the code, often complicated by poor internal documentation. The subtle
characteristics such as program structure, global data structure, system interfaces
and performance & design constraints are difficult to handle and are often
misinterpreted. The amounts of changes that are made to the code are difficult to
access.
27
CHAPTER – 5
SCREENSHOT
28
29
30
31
32
33
34
35
CHAPTER – 6
CODING
Login Form Coding:
Private Sub cancel_Click()

End
End Sub
Private Sub login_Click()

Adodc1.RecordSource = "select *from login where Username='" + Text1.Text + "'
and Password='" + Text2.Text + "'"
Adodc1.Refresh
If Adodc1.Recordset.EOF Then
MsgBox "login failed,try again...!!!", vbCritical, "Please Enter correct Username
and Password"
Else
MsgBox "Login successful", vbInformation, "Successful attempt"
Form10.Show
End If
End Sub
Progress Bar Form Coding:
Dim ctr, ctr2, r As Double

Dim ctr3 As String
Private Sub Form_Load()
Timer1.Enabled = True
End Sub
36
Private Sub Timer1_Timer()
Label1.Caption = "Loading....."
ctr = 0
If ctr2 <= 100 Then
Randomize
r = Int((200 - 100 + 1) * Rnd + 100)
ctr = r / 122
ctr = Round(ctr, 0)
ctr = ctr2 + ctr
ctr3 = Str(ctr)
If ctr >= 100 Then
Label2.Caption = "100%"
Shape2.Width = 12795
MDIForm1.Show
Unload Me
Else
Shape2.Width = Shape2.Width + r
Label2.Caption = (ctr3) + "%"
ctr2 = Int(ctr3)
End If
End If
End Sub
MDI Form Coding:
Private Sub addcompany_Click()

Form2.Show
End Sub
Private Sub balancesheet_Click()

Form8.Show
End Sub
Private Sub companydtls_Click()

DataReport2.Show
37
End Sub
Private Sub exit_Click()

End
End Sub
Private Sub listofcompany_Click()

Form3.Show
End Sub
Private Sub profitloss_Click()

Form7.Show
End Sub
Private Sub purchase_Click()

Form4.Show
End Sub
Private Sub purchasedtls_Click()

DataReport3.Show
End Sub
Private Sub sales_Click()

Form5.Show
End Sub
Private Sub salesdtls_Click()

DataReport4.Show
End Sub
Private Sub stock_Click()

Form6.Show
End Sub
38
Add Company Form Coding:
Private Sub Command1_Click()

On Error GoTo errmsg
Adodc1.Recordset.Update
MsgBox "Successfully saved"
Exit Sub
errmsg:
MsgBox "Error in saving"
End Sub

confirmation = MsgBox("Do you want to delete this record", vbYesNo + vbCritical,
"Delete Record Confirmation")
If confirmation = vbYes Then
Adodc1.Recordset.Delete
MsgBox "Record has been delete this record", vbYesNo + vbCritical,
vbInformation, "Message"
End If
Exit Sub
errmsg:
MsgBox "Cannot delete this row or select row to delete"
End Sub

MDIForm1.Show
Unload Me
End Sub

Adodc1.Recordset.AddNew
Exit Sub
errmsg:
MsgBox "Error in adding"
End Sub
39
End Sub
List of Company Form Coding:

Adodc1.Recordset.MoveNext
Exit Sub
errmsg:
MsgBox "There is no more Next"
End Sub

Adodc1.Recordset.MovePrevious
Exit Sub
errmsg:
MsgBox "There is no more Previous"
End Sub

Adodc1.RecordSource = " select * from company where Name = '" + Text1.Text +
"'"
Adodc1.Refresh
MsgBox "Record not found", vbCritical, "Message"
Else
Adodc1.Caption = Adodc1.RecordSource
End If
End Sub

40
Adodc.Recordset.Delete
MsgBox "Record has been deleted successfully", vbInformation, "Message"
Else
MsgBox "record not Deleted !!!", vbInformation, "Message"
End If
Exit Sub
errmsg:
End Sub

Adodc1.RecordSource = "select *from company"
Adodc1.Refresh
End Sub

MDIForm1.Show
Unload Me
End Sub
Purchase Form Coding:

Exit Sub
errmsg:
End Sub

Text27.Text = Val(Text16.Text) * Val(Text20.Text)
End Sub

41
End Sub

End Sub

End Sub

End Sub

End Sub

Form6.Show
End Sub

DataEnvironment6.purchase Text30
DataReport6.Show
DataReport6.Refresh
DataEnvironment6.rspurchase.Close
End Sub

Exit Sub
errmsg:
End Sub
42
MsgBox "Record has been deleted successfully", vbInformation, "Message"
Else
MsgBox "record not Deleted !!!", vbInformation, "Message"
End If
Exit Sub
errmsg:
End Sub

MDIForm1.Show
Unload Me
End Sub

Exit Sub
errmsg:
End Sub

Exit Sub
errmsg:
End Sub
43
Adodc1.RecordSource = "select *from purchase where PurchaseID='" +
Text31.Text + "'"
Adodc1.Refresh
Else
End If
End Sub

End Sub

Text29.Text = Val(Text22.Text) + Val(Text23.Text) + Val(Text24.Text) +
Val(Text25.Text) + Val(Text26.Text) + Val(Text27.Text) + Val(Text28.Text)
End Sub

End Sub
Private Sub w_Click()

Adodc1.RecordSource = "select *from purchase"
Adodc1.Refresh
End Sub
Sales Form Coding:

DataEnvironment1.Bill Text18
DataReport1.Show
DataReport1.Refresh
DataEnvironment1.rsBill.Close
End Sub
44
Adodc2.RecordSource = "select *from stock where StockNumber='" + Text15.Text
+ "'"
Adodc2.Refresh
Else
End If
End Sub

Adodc1.RecordSource = "select *from sales1"
Adodc1.Refresh
End Sub

Form6.Show
End Sub

Exit Sub
errmsg:
End Sub

End Sub

45
End Sub

End Sub

End Sub

End Sub

End Sub

End Sub

MsgBox "Record has been delete this record", vbYesNo + vbCritical,
vbInformation, "Message"
End If
Exit Sub
errmsg:
End Sub
46
MDIForm1.Show
Unload Me
End Sub

Exit Sub
errmsg:
End Sub

Exit Sub
errmsg:
End Sub

Adodc1.RecordSource = " select * from sales1 where SaleID = '" + Text43.Text + "'"
Adodc1.Refresh
Else
End If
End Sub

Exit Sub
errmsg:
End Sub
47
End Sub

End Sub
Stock Form Coding:

Adodc1.RecordSource = " select * from stock where StockNumber = '" +
Text42.Text + "'"
Adodc1.Refresh
Else
End If
End Sub

Exit Sub
errmsg:
MsgBox "Error in Adding"
End Sub

MDIForm1.Show
Unload Me
End Sub

48
Exit Sub
errmsg:
End Sub

Form4.Show
Unload Me
End Sub

Form5.Show
Unload Me
End Sub

Form7.Show
Unload Me
End Sub
Profit \Loss Form Coding:
Text51.Text = Val(Text44.Text) - Val(Text37.Text)
End Sub

End Sub

End Sub

End Sub
49
End Sub

End Sub

Exit Sub
errmsg:
End Sub

MDIForm1.Show
Unload Me
End Sub

DataEnvironment5.profitloss Text2
DataReport5.Show
DataReport5.Refresh
DataEnvironment5.rsProfitloss.Close
End Sub

Exit Sub
errmsg:
End Sub
50
Form6.Show
End Sub

End Sub

Form8.Show
Unload Me
End Sub

Adodc2.RecordSource = " select * from sales1 where SaleID = '" + Text1.Text + "'"
Adodc2.Refresh
Else
End If
End Sub

Adodc1.RecordSource = " select * from ploss where AccountID = '" + Text66.Text +
"'"
Adodc1.Refresh
Else
End If
End Sub

51
End Sub

End Sub

End Sub

End Sub

End Sub

End Sub

End Sub

End Sub
Balancesheet Form Coding:
End Sub
52
Exit Sub
errmsg:
End Sub

Exit Sub
errmsg:
End Sub

MDIForm1.Show
Unload Me
End Sub

Form9.Show
Unload Me
End Sub

End Sub

End Sub

End Sub
53
End Sub

End Sub

End Sub

End Sub

End Sub

Adodc1.RecordSource = " select * from balance where BalanceID = '" + Text5.Text
+ "'"
Adodc1.Refresh
Else
End If
End Sub

Form7.Show
End Sub
54
date1 = Format(DTPicker1.Value, "dd-mm-yyyy")
date2 = Format(DTPicker2.Value, "dd-mm-yyyy")
If date2 < date1 Then
MsgBox "Please Select the correct date:End date cannot be lesser than Start
Date", vbCritical, "Warning Message"
Else
Adodc1.RecordSource = "select *from balance where Year between # " & date1 &
" # and # " & date2 & " #"
Adodc1.Refresh
MsgBox "Record not found,Please Enter Correct Date", vbCritical, "Warning
Message"
Else
End If
End If
End Sub

Text71.Text = Val(Text72.Text) + Val(Text73.Text)
End Sub

End Sub

End Sub

End Sub

55
End Sub

End Sub

End Sub

End Sub
Balancesheet Form Coding:
+ "'"
Adodc1.Refresh
Else
End If
End Sub

DataEnvironment7.balance Text18
DataReport7.Show
DataReport7.Refresh
DataEnvironment7.rsbalance.Close
End Sub

+ "'"
Adodc2.Refresh
56
Else
End If
End Sub

+ "'"
Adodc3.Refresh
Else
End If
End Sub

Adodc4.RecordSource = " select * from balance where BalanceID = '" +
Text12.Text + "'"
Adodc4.Refresh
Else
End If
End Sub

Adodc5.RecordSource = " select * from balance where BalanceID = '" +
Text15.Text + "'"
Adodc5.Refresh
Else
End If
57
End Sub

Val(Text10.Text) + Val(Text13.Text)
End Sub

Val(Text11.Text) + Val(Text14.Text)
End Sub

Exit Sub
errmsg:
End Sub

MDIForm1.Show
Unload Me
End Sub

Text2.Text = ""
Text4.Text = ""
Text7.Text = ""
Text10.Text = ""
Text13.Text = ""
Text3.Text = ""
Text5.Text = ""
Text8.Text = ""
Text11.Text = ""
Text14.Text = ""
58
Text16.Text = ""
Text17.Text = ""
End Sub
59
CHAPTER – 7
CONCLUSIONS
Our project is only a humble venture to satisfy the needs to manage their
project work. Several user friendly coding have also adopted. This package shall
prove to be a powerful package in satisfying all the requirements of the school.
The objective of software planning is to provide a frame work that enables the
manger to make reasonable estimates made within a limited time frame at the
beginning of the software project and should be updated regularly as the project
progresses.
At the end it is concluded that we have made effort on following

points…
 A description of the background and context of the project and its relation
to work already done in the area.
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions
that can be done on these things.
 We understand the problem domain and produce a model of the system,
which describes operations that can be performed on the system.
 We included features and operations in detail, including screen layouts.
 We designed user interface and security issues related to system.
 Finally the system is implemented and tested according to test cases.
It is the complete accounting software is so designed as to ease the work load

of accounting professionals. The main feature includes invoicing, inventory and
stock control, accounting, client and vendor management.
60
SCOPE FOR FUTHER ENHANCEMENT:
In a nutshell, it can be summarized that the future scope of the project circles
around maintaining information regarding:
 We can add printer in future.

 We can give more advance software for Accounting System including more
facilities.
 We will host the platform on online servers to make it accessible worldwide
Integrate multiple load balancers to distribute the loads of the system.
 Create the master and slave database structure to reduce the overload of
the database queries.
 Implement the backup mechanism for taking backup of codebase and
database on regular basis on different servers.
The above mentioned points are the enhancements which can be done to
increase the applicability and usage of this project. Here we can maintain the
records of Accounts. Also, as it can be seen that now-a-days the players are
versatile, i.e. so there is a scope for introducing a method to maintain the
Accounting System. Enhancements can be done to maintain all the Accounts,
Stocks, Company, Inventory.
We have left all the options open so that if there is any other future requirement
in the system by the user for the enhancement of the system then it is possible to
implement them.In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will
serve its purpose for which it is develop there by underlining success of process.
61
BIBLIOGRAPHY:
The following books were referred during the analysis and execution phase of the
project.
VISUAL BASIC 6.0 PROGRAMMING

-By Steven Holzner.
MSDN 2002
-By Microsoft.
62

Visual Basic 6.0 Project On Accounting System

Uploaded by

Document Information

Original Title

Copyright

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Visual Basic 6.0 Project On Accounting System

Uploaded by

Copyright:

CHAPTER-1

1.1 Background Study:

Accounting is the language of business. It is the system of recording,

However, historically, accounting systems were a complex series of manual

1.1.1 The organization profile:

1.1.2 Study of the existing system:

1.2 Project overview:

1.3 Objective of the project:

 It is situated for all level of peoples.

Important features of this proposed system are:

OBJECTIVES OF THE PROPOSED SYSTEM

 To reduce workload of staff.

2.1.1 Problem definition:

2.2 SYSTEM REQUIREMENT:

2.3 SOFTWARE JUSTIFICATION:

Microsoft Visual Basic 6.0 is the powerful programming language to develop

MICROSOFT VISUAL BASIC 6.0

Visual Basic 6.0 is an enjoyable language due to its visual environment.

SIGNIFICANCE FEATURES OF VISUAL BASIC 6.0

Value Named constant Description

FOLLOWING ARE THE CUSTOM CONTROLS, WHICH ARE

UNDERSTANDING THE EVENT-DRIVEN MODEL

USER INTERFACE ELEMENTS

DATA BASE CONNECTIVITY

Back End Tool [MS-Access]

MS-Access is a RDBMS, offers capabilities of both Relational and Object Oriented

DBMS or RDBMS: -The Database Management System is the software and

Query: -A query is a read-only transaction against a database. A query is

Schema: -A schema is a collection of objects associated with the database.

2.4 COST ESTIMATION AND SCHEDULING:

* Hardware & software cost,

Scheduling as well as estimating the effort required to develop the software

3.1 Design Notations:

3.1.1 Data Flow Diagram:

Zero level Data Flow Diagram:

3.2.1 Database design:

3.2.3 OUTPUT DESIGN

Black Box Testing

User Acceptance Testing

4.2 SYSTEM IMPLEMENTATION:

4.2.1 Implementation Procedures :

4.2.2 Operational Documentation:

We may define Software Maintenance by describing four activities that are

Login Form Coding:

Private Sub cancel_Click()

Private Sub login_Click()

Dim ctr, ctr2, r As Double

Private Sub addcompany_Click()

Private Sub balancesheet_Click()

Private Sub companydtls_Click()

Private Sub exit_Click()

Private Sub listofcompany_Click()

Private Sub profitloss_Click()

Private Sub purchase_Click()

Private Sub purchasedtls_Click()

Private Sub sales_Click()

Private Sub salesdtls_Click()

Private Sub stock_Click()

Private Sub Command1_Click()

Private Sub Command2_Click()

Private Sub Command3_Click()

Private Sub Command4_Click()

Private Sub Command1_Click()

Private Sub Command2_Click()

Private Sub Command3_Click()

Private Sub Command4_Click()