CHAPTER I

1. INTRODUCTION

1.1 ABOUT THE PROJECT

Vegetable Market Maintenance System is a software application maintains the records

related to vegetable market.

The “Vegetable Market Maintenance System” is fully integrated with vegetable

market requirement and enhances the capabilities of the current system, since the new system
is a Graphical User Interface oriented application. It allows security features by providing
various right and privileges in according the data. All this aspects will enable the business to
function as an independent system. It also provides the latest technology embedded in the
system, which will yield the desired result.

OBJECTIVE

The main objective of the application is to automate the existing system of manual
entry maintain the records of the Customer details, Supplier details, product details, purchase
details, sales details, stock details, employee details.

Vegetable Market Maintenance System provides stylish interface for evaluating the
vegetable market management, the ratings will be stored securely and it’s archived in a
central location for the future.

PROBLEM DEFINITION

The application should provide quick access to the records maintained and must reveal
the important reviews about the business so that the growth can be easily compared and
should provide with the various reports showing the related details so that the important
decisions could be taken easily.

1
 CHAPTER II
2. SYSTEM STUDY
2.1. EXISTING SYSTEM

It consists of keeping all the details about purchase details and product sales bill
details. There is a lot of reason for the introduction of this project. In this System old version
of FoxPro, there are number of inefficiencies that a management faces of report generator.
The information retrieval is one of the foremost problems. It is very difficult to gather the
overall performance reports of the transaction. In this system delay to retrieving record with
in second.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

• Slow process
• No crystal report access.
• Time consuming
• No direct role for the higher officials

2.2 FEASIBILITY STUDY

Feasibility Analysis is the measure of how to benefits or practical development of an

information system. There are three categories of feasibility analysis

 Technical feasibility
 Operational feasibility
 Economic feasibility
The proposed system should feasible in all these three aspects.

2.2.1 TECHNICAL FEASIBILITY

To decide whether a project is technically feasible, should consider technical issues

involved in the system. It is evident that necessary hardware and software available for
development and maintenance of the proposed system. Hence the solution is technically
feasible.

2
2.2.2 OPERATIONAL FEASIBILITY

To determine operational feasibility of system should take into awareness of user. The
system should be user friendly and east to use. This essentially means that the system should
be simple and easy to operate and the performance produced should be high. So the system is
operationally feasible. All basic tables have been indexed on their primary keys, thereby
increasing the speed of retrieval. Operation feasibility is the measure of people feel about the
system.

2.2.3 ECONOMIC FEASIBILITY

Economic feasibility deals with the cost and benefit the information system. Technical
feasibility is computer oriented. Operational feasibility is people oriented. To decide whether a
project economically feasible, we have to take into consideration various factors such as

 Cost Benefit Analysis

 Long Term Analysis
 Maintenance Cost
Economic feasibility is the measure of the cost effectiveness of the project or solution. It is
the measure of whether a solution will be profitable. By developing this project, the company
can reduce manpower so that they can get better benefit. The maintenance cost of the system
enhances the profitability.

3
2.3. PROPOSED SYSTEM

In this system using visual basic .net application for crystal report method and it’s easy
for the user to meet the challenges of managing their records and retrieval of useful
information. The application covers the area of client information, invoice, product etc and
product in hand and delivered information. The system revolves around the menu of the
product available. The user can browse through the menu to get the desired information. The
project is very flexible because it allows the user to get information in various possible
categories. Everything is done dynamically. All the details are stored into appropriate
database. The functionality of the proposed system includes the following: Customer
information , Product information Quantity in hand Delivered stock The admin can find
relevant data in each module itself. admin can modify, delete, update, view, or inset new data
as when required. Performing these tasks is a very simple task in the product and the user can
do it quite easily. The database is connected dynamically to front-end so that any changes
made to database are immediately reflected to the user

2.3.1 ADVANTAGES OF PROPOSED SYSTEM

 File maintenance is easy.

 Information can be retrieved within a fraction of seconds.
 Overcomes the lack of accuracy.
 It enhances the security mechanism

4
 CHAPTER III

3.SYSTEM SPECIFICATIONS

3.1. HARDWARE CONFIGURATION

Processor : Intel Pentium Processor

Speed : 3.2 MHz

Memory : 1 GB RAM

Display : 17”color monitor

Storage : 80 GB HDD

Keyboard : DCOM 104 keys

Pointer device : 3 buttons optic scroll mouse

3.2 SOFTWARE CONFIGURATION

Front End : Visual Basic .Net 2008

Back End : MS-ACCESS

5
SOFTWARE FEATURES

Front End: Visual Basic .NET 2008

Visual Basic .NET is an object orientated programming language which is a

combination of Microsoft’s Visual Basic in conjunction with the .NET framework. VB .NET
was designed by Microsoft to increase the development speed of GUI applications for the
Windows platform.

Visual Basic was originally designed to be easy to use and learn, while making the
development of simple graphical programs easy, visual basic also offers many powerful
features for the development of large and complex applications.

The .NET framework is a large library of code created to reduce the amount of
common programming problems. The framework uses an application virtual machine created
by the (CLR). The CLR (Common Language Runtime) allows developers to produce code
without worrying about capabilities of the CPU; this is all handled by the CLR. The CLR
manages code that was written directly for the .NET framework.

One of Visual Basic’s biggest downfalls and the very reason it was avoided by some
developers was its limitations to only run under Windows.

Visual Basic can now be run on other platforms such as Linux; this is made possible
by Mono. Mono is an open-source development platform which has created a Visual Basic
compiler, written in Visual Basic which will allow compiling and running off VB scripts on
any operating system that supports mono.

Some downsides to using the .NET framework are that older versions of windows do
not have .NET installed and developers feel that the size of the package is sometimes big
enough to put the end user off installing the framework.

6
Menu Bar

Displays the commands you use to work with Visual Basic.Net Besides the standard
File, Edit, View, Window and Help menus, menus are provided to access functions specific to
programming such as Project, Format or Debug.

Context Menus

To open a context menu, click the right mouse button on the object you are using. The
specific list of shortcuts available from context menus depends on the part of the environment
where you click the right mouse button.

Toolbar

Provide quick access to commonly used commands in the programming environment.

You click a button on the toolbar once to carry out the action represented by that button+. By
default, the standard toolbar is displayed when you start Visual Basic.Net.

Tool Box

Provide a set of tools that you use at design time to place controls on a form. In
addition to the default toolbox layout, you can create your own custom layouts by selecting
Add tab from the context menu and adding controls to the resulting tab.

Project Explorer Window

List the forms and module in your current project. A project is the collection of files
you use to build an application.

Properties Window

List the property setting for the selected forms or control. A property is a
characteristic of an object, such as size, caption or color.

7
Object Browser

List objects available for use in your use in your project and gives you a quick way to
navigate through your code. You can use the Object Browser to explore objects in Visual
Basic and properties are available for those objects, and paste code procedures into your
application.

Forms Designer

Serves is a window that you customize to design the interface of your application.
You add controls, graphics and pictures to a form to create the look you want. Each form in
your application has its forms designer window.

Code Editor Window

Serves is an editor for entering application code. A separate code editor windows
Are created for each form or module in your application.
Multiple Document Interface (MDI)

MDI stands for multiple document interfaces. A multiple document interface is used
for opening many windows as the same time. All the document windows are contained in a
parent window, which provides a workspace in the application. Visual Basic applications can
have only one MDI forms, which contains all the child forms.

ActiveX Control

An ActiveX control is an extension to the Visual Basic Tool box. You can use ActiveX
controls just as you would use any of the standard built-in controls. When you add an
ActiveX control, it becomes part of the development and run-time environment and provides
new functionality for your application.

For our first VB IDE post on the VB team blog, I’d like to give you my list of the top
10 new features in the Visual Studio 2005 IDE. Now that the product has been released, you
can take advantage of these today!

8
BACK END: MS-ACCESS

This database lets us to store and organize information in sets of tables. After creating
a database we can look in information as a list (in columns and rows) or we can look at the
information in a form as though it were recorded on an index card. Microsoft Access provides
two ways to create a table. It can create a blank (empty) table for entering own data, or It can
create a table using existing data from another source. A table is a collection of data about a
specific topic.

Terms and Definitions:

Field

The smallest piece of data in a table.

Cell

Where one row and one column intersect on a table.

Record

A collection of all fields relating to one person, place, or thing occupying a single row
of a table.

Table

A collection of records with one record occupying a single row with one or many
fields per Row. A database can consist of multiple tables.

Query

Asks specific questions about the data in the database.

Forms

A method of entering, displaying, and searching data in other than the Spreadsheet-like
environment of tables and queries (a graphical user interface).

Reports

Summarizes and formats data in the "look" that want for either table or query data.

Object

Components that make up a database (i.e., tables, forms, queries, reports, macros &
modules).

9
Primary Key

Primary key and foreign keys are using the table. Primary keys determine every
record in a table.

Foreign Key

Foreign key is a field used to use to set the relationship with another tables.

The Salient Features of Microsoft Access:

This database lets us to store and organize information in sets of tables. After creating
a database we can look in information as a list (in columns and rows) or we can look at the
information in a form as though it were recorded on an index card. Microsoft Access provides
two ways to create a table. It can create a blank (empty) table for entering own data, or It can
create a table using existing data from another source. A table is a collection of data about a
specific topic.

10
 CHAPTER IV

4. SYSTEM DESIGN

4.1 INPUT DESIGN

Once the analysis and design of the system has been done, it would be necessary to
identify the data that are required to be processed to produce the outputs. Input is one of the
most expensive phases of the operation of a computerized system and creates sometimes a
major problem. Different type of problem with a system can usually be traced back to faulty
input design method needless to say, therefore, that the input data are the lifeblood of a
system and have to be analyzed and designed with utmost care and consideration. Input
design features can ensure the reliability of the system and generate correct reports form the
accurate data.

Input design is the process of converting To ensure that the input is understood by the
user Input design is one of the most expensive phases of the operation of computerized
system and is often the major problem of a system. A larger number of problem with a system
can usually be traced back to fault input design and method. Needless to say, therefore that
the input data is the life block of a system and has to be analyzed and designed with the most
consideration.

Input design is a part of overall system design, requires the very careful analysis of the
input data product. The goal of the input design is to make the data entry easier, logical and
free from errors. The user controls input data. The commonly used input, output devices are
mouse, keyboard and the visual display unit. The well designed, well organized screen
formats are used to acquire the inputs. The data accepted is stored on database file. Our
system is classified into subsystem such as
 Customer
 purchase
 purchase return
 sales
 stock

11
4.2 OUTPUT DESIGN

Presenting the data processed by a computer-based information system in an attractive

and usable form has become very essential these days’ success and acceptance of a system to
some extent depends on good presentation. Therefore, system analyst must know fully how to
design output report in an attractive way. Many new output devices are being introduced in
the market because of recent development in computer technology. System analyst must be
aware of these new technologies and try to use these new output devices if possible.
Currently, excellent graphic displays are widely available. Speech output systems are also
fast emerging.

Output design generally refers to the results and information that are generated by the system.
For many end users, output is the main reason for developing the system and the basis on
which they evaluate the usefulness of application.

The objective of a system finds its shape in terms of the output. The analysis of the
objective of a system leads determination of outputs. Outputs of a system can take various
forms. The most common are reports, screen displays, and printed form, graphical drawing
etc. the outputs also vary in terms of their contents, frequency, timing and format. The users
of the output, its purpose and sequence of details to be printed are all considered. The output
from a system is the justification for its existence. It the outputs are inadequate in any way,
the system itself is inadequate. The basic requirements of output are it should be accurate,
timely and appropriate in terms of content, medium and layouts for its intended purpose.
Hence it is necessary to design output so that the objectives of the system are met in the best
possible manner. The outputs are in the form of reports.

4.3. TABLE DESIGN

Normalization

Normalization is procedure to ensure that a data model confirms to some useful

standards, such as

To minimize the duplication of data.

To provide the feasibility necessary to support different functional requirements.

12
First Normal Form:

In this normal form, repeating attributes are removed and the attributes are placed in
corresponding entities.

Second Normal Form:

In this normal form, the attributes that are not dependent on the unique identifier are
removed, i.e. every non-key attributes should be fully dependent on primary key. In the
project, to identify the product uniquely, an attributes product product id is created as the
primary key. In the project, to identify the product uniquely, an attribute product id is created
with constraint unique and not null.

Third Normal Form:

In this form, every non-key attributes are non-transitively dependent on the primary
key. In technical support module, the non-key attributes problem, solution, date requested is
not dependent on the reports.

4.3.1 DESCRIPTION OF MODULES

Login Details

The Login Module deals with the information about Admin (i.e.) User Name, Password

Customer Details

The customer Module deals with the information about customer (i.e.)
customer_code, Name , Address, Phone etc. the customer orders are recorded and maintained
and the delivery is done according to the priority. This module also includes the details about
the bills produced for the customer during sales.

Product Details

The Product Module deals with the information about Product Codes, Product Name,
Type, Units, Purchase Rate, Sales rate and their description. The stock level has to be
monitored regularly in product module and the purchase price and sales price are also
maintained by the module.

13
Supplier Details

The Supplier Module deals with the information about Product Supplier (i.e.)
Supplier code, Supplier Name , Address, Phone, Email id etc. the supplier are recorded and
maintained and the purchase is done according to the priority.

Purchase Details

Purchase Invoice no, Invoice Date, Supplier code, Supplier name, Product code,
product name, Unit, Purchase qty, Rate, Amount and Net Amount, It deals with the
generation of purchase invoice for the required stock during purchase.

Purchase Return Details

This purchase return details deals with information about Purchase Return no, Return
Date, Supplier code, Supplier name, Product code, product name, unit,Return qty.

Sales Billing Details

Sale Invoice no, Sale Date, Customer name, address, product code, product name,
unit, Sale qty, Rate, Amount, Bill Amount, The Sales Invoice Module deals with the sales of
final product to the customer. It deals with the generation of sales invoice for the required
stock during sales. It also deals with the generation of sales bill and the payment details of the
customer.

Stock Details

This stock details deals with information about of stock date, product code, product
name, unit, purchase Quantity, Sale Quantity, Stock Quantity. The stock Module checks the
stock level continuously.

Employee Details

This stock details deals with information about of Employee code, Employee name,
address, contact no, date of joining and salary.

14
TABLE NAME:LOGIN

S.NO FIELD DATA TYPE SIZE DISCRIPTION

1 U_NAME TEXT 30 USER NAME
2 PASS TEXT 30 PASSWORD

TABLE NAME: CUSTOMER DETAILS

PRIMARY KEY: C_ID

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 C_ID TEXT 10 CUSTOMER ID

2 C_NAME TEXT 30 CUSTOMER NAME

3 C_ADDRE TEXT 50 ADDRESS

4 PH_NO NUMBER 10 PHONE NUMBER

TABLE NAME: PRODUCT DETAILS

PRIMARY KEY: PCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 PCODE TEXT 10 PRODUCT CODE

2 PNAME TEXT 30 PRODUCT NAME

3 PDES TEXT 30 PRODUCT DESCRIPTION

4 UNIT TEXT 10 UNIT

5 PRATE NUMBER 5 PURCHASE RATE

6 SRATE NUMBER 5 SALES RATE

15
TABLE NAME: SUPPLIER DETAILS

PRIMARY KEY: S_CODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 S_CODE TEXT 10 SUPPLIER CODE

2 S_NAME TEXT 30 SUPPLIER NAME

3 ADDRE TEXT 50 ADDRESS

4 PH_NO NUMBER 10 PHONE NUMBER

5 EID TEXT 30 EMAIL ID

TABLE NAME: PURCHASE DETAILS

PRIMARY KEY: PINV_NO

FOREIGN KEY:PCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 PINV_NO NUMBER 5 INVOICE NUMBER

2 P_DATE DATE - PURCHASE DATE

3 S_CODE TEXT 10 SUPPLIER CODE

4 SNO NUMBER 5 SERIAL NUMBER

5 PCODE TEXT 10 PRODUCT CODE

6 PQTY NUMBER 5 PURCHASE QUANTITY

7 AMT NUMBER 5 AMOUNT

8 P_AMT NUMBER 5 PURCHASE AMOUNT

16
TABLE NAME: PURCHASE RETURN DETAILS

PRIMARY KEY: RET_NO

FOREIGN KEY:PCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 RET_NO NUMBER 10 RETURN NUMBER

2 RET_DATE DATE - RETURN DATE

3 S_CODE TEXT 10 SUPPLIER CODE

4 SNO NUMBER 5 SERIAL NUMBER

5 PCODE TEXT 10 PRODUCT CODE

6 PNAME TEXT 30 PRODUCT NAME

7 RQTY NUMBER 5 RETURN QUANTITY

TABLE NAME: SALES INVOICE DETAILS

PRIMARY KEY: SINV_NO

FOREIGN KEY:PCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 SINV_NO NUMBER 10 SALE INVOICE NUMBER

2 SINV_DATE DATE - SALE INVOICE DATE

3 C_CODE TEXT 10 CUSTOMER CODE

4 PCODE TEXT 10 PRODUCT CODE

5 QTY NUMBER 5 QUANTITY

6 TOT_AMT NUMBER 5 TOTAL AMOUNT

7 BAMT NUMBER 5 BILL AMOUNT

17
TABLE NAME: STOCK DETAILS

FOREIGN KEY:PCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 ST_DATE DATE - STOCK DATE

2 PCODE TEXT 10 PRODUCT CODE

3 P_QTY NUMBER 5 PURCHASE

QUANTITY

4 S_QTY NUMBER 5 SALES QUANTITY

5 ST_QTY NUMBER 5 STOCK QUANTITY

6 RE_LEVEL NUMBER 5 RE-ORDER LEVEL

TABLE NAME: EMPLOYEE DETAILS

PRIMARY KEY:EMPCODE

SNO FIELDS DATA TYPE SIZE DESCRIPTION

1 EMPCODE TEXT 10 EMPLOYEE CODE

2 EMPNAME TEXT 30 EMPLOYEE NAME

2 ADDRESS TEXT 100 ADDRESS

3 C_NO NUMBER 10 CONTACT NUMBER

4 DOJ DATE - DATE OF JOINING

5 SAL NUMBER 5 SALARY

18
 4.4 DATA FLOW DIAGRAM

1
Username, password Process to
Login Login Details
Login
Process

Product code, 2 Process to

Product Entry name Product Details
Product data
Process

Supplier code,
3
name
Supplier Entry Process to
Supplier Details
Supplier
Process data

4
Purchase no, Process to data
Purchase Entry Date,P Code, Purchase Details
Purchase
name Process
Reports B

Return qty, return 5

Return Entry date, supplier Process to data Purchase return Details
name Return
Process

Reports C

19
 A

ccode,cname
7 Process to
address
Customer Entry Customer Details
Customer
Process

sale date,
Process to data
8
Sales Entry sale qty Sales Details
Sales
process

Report
B
Stock date, C
pqty, sqty, 9
Stock Entry Process to
Stock Details
Stock data
Process

Report
Process to
Emp code,salary data
10
Employee Entry Employee details
Employee
Process

20
 CHAPTER V

5. SYSTEM TESTING AND IMPLEMENTATION

5.1. SYSTEM TESTING

System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results. An example of system testing
is the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integrated points.

Testing Objectives:

The main objective of testing is to uncover a host of errors, systematically and with minimum
effort and time. Stating formally, we can say,

 Testing is a process of executing a program with the intent of finding an error.

 A successful test is one that uncovers an as yet undiscovered error.
 A good test case is one that has a high probability of finding error, if it exists.
 The tests are inadequate to detect possibly present errors.
 The software more or less confirms to the quality and reliable standards.

5.1.1 UNIT TESTING

The primary goal of unit testing is to take the smallest piece of testable software in the
application, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules to
test the interfaces between modules. Unit testing has proven its value in that a large
percentage of defects are identified during its use.

Unit testing is a software verification and validation method where the programmer
gains confidence that individual units of source code are fit for use. A unit is the smallest
testable part of an application. In procedural programming a unit may be an individual
program, function, procedure, etc., while in object-oriented programming, the smallest unit is
a class, which may belong to a base/super class, abstract class or derived/child class.

21
 Ideally, each test case is independent from the others: substitutes like method stubs,
mock objects, fakes and test harnesses can be used to assist testing a module in isolation. Unit
tests are typically written and run by software developers to ensure that code meets its design
and behaves as intended. Its implementation can vary from being very manual (pencil and
paper) to being formalized as part of build automation.

5.1.2. INTRGRATION TESTING:

Integration testing, also known as integration and testing (I&T), is a software

development process which program units are combined and tested as groups in multiple
ways. In this context, a unit is defined as the smallest testable part of an application.
Integration testing can expose problems with the interfaces among program components
before trouble occurs in real-world program execution. Integration testing is a component of
Extreme Programming (XP), a pragmatic method of software development that takes a
meticulous approach to building a book by means of continual testing and revision.

There are two major ways of carrying out an integration test, called the bottom-up
method and the top-down method. Bottom-up integration testing begins with unit testing,
followed by tests of progressively higher-level combinations of units called modules or
builds. In top-down integration testing, the highest-level modules are tested first and
progressively lower-level modules are tested after that. In a comprehensive software
development environment, bottom-up testing is usually done first, followed by top-down
testing.

22
5.1.3. USER ACCEPTANCE TESTING

User acceptance of a system is the key factor of the success of any system. The
system under study is tested for the user acceptance by constantly keeping in touch with the
prospective system users at the time of developing and making changes wherever required.

5.1.4. OUTPUT TESTING

After performing the validation testing, the next step is output testing of the proposed
system since no system could be useful if it does not produce the required output in the
specific format. The output generated or displayed by the system under consideration is tested
by asking the user about the format is considered in two ways, one is on the screen and
another is printed format.

5.1.5. VALIDATION TESTING:

At the conclusion of integration testing software is completely assembled as a

package, interfacing errors have been uncovered and corrected and a final series of software
tests begins, validation test begins. Validation test can be defined in many ways. But the
simple definition is that validation succeeds when the software function in a manner that can
reasonably expected by the customer. After validation test has been conducted one of two
possible conditions exists.

One is the function or performance characteristics confirm to specifications and are

accepted and the other is deviation from specification is uncovered and a deficiency list is
created. Proposed system under consideration has been tested by using validation testing and
found to be working satisfactorily.

23
5.2. SYSTEM IMPLEMENTAION
The implementation plan includes a description of all the activities that must occur to
implement the new system and to put into operation. It identifies the personnel responsible
for the activities and prepares a time chart for implementation the system.

System implementation is an important stage of the project where the theoretical

design is turned into practical system .the system can be implemented only after through
testing is done and if it is found to work according to the specification.

The problems encountered are converting files, training users, creating accurate are
converting files and verifying printouts for integrity.

A post implemented overview measures the system performance against predefined

review determines how well the system continues to meet performance specifications. A post
implementation review is an evaluation of the system in terms to which the system
accomplishes stated objectives and actual project work exceeds initial estimates

24
 CHAPTER VI

6.CONCLUSION

After we have completed the project we are sure the problems in the existing system
would overcome. The “vegetable market maintenance system” process made computerized to
reduce human errors and to increase the efficiency. The main focus of this project is to lessen
human efforts. The maintenance of the vegetable market maintenance system is made
efficient, as all the records are stored in the access database, through which data can be
retrieved easily. The product order and delivery are given a particular unique id no. So that
they can be accessed correctly and without errors. Our main aim of the project is to get the
correct information about a particular customers and sales details available in the vegetable
market.

The problems, which existed in the earlier system, have been removed to a large extent.
And it is expected that this project will go a long way in satisfying users requirements. The
computerization of the vegetable market will not only improves the efficiency but will also
reduce human stress thereby indirectly improving human recourses.

25
 CHAPTER VII

7. BIBLIOGRAPHY

Mastering Visual Basic .Net : Stven Holzner dream, First Edition 2002

MS-Access : Joycox

Software Engineering : By Roger Pressman

System Analysis and Design : By Elias M.A. Wad,

Galgotia Publications 1997 Edition

Fundamentals of Database Systems : Shamkant B. Navathe.

Websites Referred

1.www.vbdotnetheaven.com

2.www.w3school.com

3.www.wikipedia.com

www.vbtutorial.com

5.www.vbsourcecode.com

26
 CHAPTER VIII
8.APPENDIXES
8.1. Screens Shots

Fig 1: LOGIN FORM.

27
Fig 2:MASTER FORM.

28
Fig 3: PRODUCT DETAILS FORM

29
Fig 4: CUSTOMER DETAILS FORM

30
Fig 5: EMPLOYEE DETAILS FORM

31
Fig 6: SUPPIER DETAILS FORM

32
Fig 7: TRANSACTION MASTER FORM

33
Fig 8: PURCHASE DETAILS FORM

34
Fig 9: PURCHASE RETURN DETAILS FORM

35
Fig 10: SALES BILL DETAILS FORM

36
Fig 11: STOCK DETAILS FORM

37
8.2. Reports

Fig 12: REPORT DETAILS MASTER FORM

38
Fig 13: PURCHASE REPORT FORM

39
Fig 14: PURCHASE RETURN REPORT FORM

40
Fig 15: SALES REPORT FORM

41
Fig 16: STOCK REPORT FORM

42
 8.3.Sample coding

Imports System.Data
Imports System.Data.OleDb
Public Class customer
Dim con As New ADODB.Connection
Dim crs As New ADODB.Recordset
Dim opt As String

Private Sub customer_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load
con.Open("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" &
System.Environment.CurrentDirectory & "\veg_data.mdb")
crs.Open("select *from customer_details", con,
ADODB.CursorTypeEnum.adOpenStatic, ADODB.LockTypeEnum.adLockOptimistic)
Fillrecords()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox1.Focus()
crs.AddNew()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button2.Click

If TextBox1.Text = "" Then

MsgBox("Enter the customer code")
ElseIf TextBox2.Text = "" Then
MsgBox("Enter the customer name")
ElseIf TextBox3.Text = "" Then
MsgBox("Enter the address")
ElseIf TextBox4.Text = "" Then
MsgBox("Enter the contact no")

Else
crs(0).Value = TextBox1.Text
crs(1).Value = TextBox2.Text
crs(2).Value = TextBox3.Text
crs(3).Value = TextBox4.Text
crs.Update()
MsgBox("Records Update Successfuly")
End If

End Sub

Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button4.Click
TextBox1.Focus()
opt = "Modify"
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button3.Click

43
 Dim s As String
s = MsgBox("Do U want to Delete", vbYesNo, "Delete")
If s = vbYes Then
crs.Delete()
MsgBox("One Record Deleted")
crs.MoveFirst()
Fillrecords()
End If
End Sub

Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button5.Click
Me.Close()
End Sub
Private Sub Fillrecords()
On Error Resume Next
TextBox1.Text = crs(0).Value
TextBox2.Text = crs(1).Value
TextBox3.Text = crs(2).Value
TextBox4.Text = crs(3).Value

End Sub

Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button6.Click
Dim Code As String
Code = Trim(InputBox("Enter the Customer Code."))
On Error Resume Next
crs.MoveFirst()
crs.Find("ccode='" & Code & "'", ,
ADODB.SearchDirectionEnum.adSearchForward, 0)
Fillrecords()
End Sub
End Class

44