CHAPTER -I

INTRODUCTION

1.1 ABOUT THE PROJECT

The project entitled “TILES SHOWROOM MANAGEMENT SYSTEM” which maintains

all the information about the titles. The goal of this project is to minimize the work done by
employee in titles product purchase maintenances and sales details.

This project involves the purchase, sales, delivery, employee, customer, are involved in the
information of main activities. Product details contain information about the titles products of
the maintenance.

Since the existing system is a manual one lot of titles work and manpower sre needed with
the existing system. Large number of ledgers of ledgers titles, records etc have to be kept for
future use and this consumer a large amount of office space.

This system facilitate easy of maintenance and to provide a quick view of all the details
according to the transaction of delivery and sales. Billing process is simple and error free. But
it is impossible in the manual system.

Searching and finding a particular detail of a agency from a large number of records needs a
large amount of time. Also the data can be lost in future. The main aim of this project
maintains the employee details and the delivery details.

This software is competent of producing reports regarding maintenance consist of various

stages. The ultimate aim of project is computerized and easily maintained of titles showroom
management system.

1
1.2 OBJECTIVES OF STUDY

 The main objective of the developing such a computerization system is to reduce the paper
work and save the time in Tails showroom management system. There by increasing the
efficiency and decreasing the work load.
 The project provides us the information about employee details, supplier details, purchase
details, customer details, sales details. The system must provide the flexibility of generating
the required documents on screen as well as on printer as when required.
 To computerize all details regarding employee details and customer details.
 To automate the process of ward entries.
 To maintain record effectively.

2
1.3 ORGANISATION PROFILE

Thiru.K.Raju started “KAILAS TRADERS” in the year 2009. It is one of the

famous tiles sales in Bharathi Nagar, veerapandi (po), Palladam Road, Tirupur. It was
established with an ultimate aim to give good rice based items to the customers.

In this shop more than 10 members are working. More than 10 families are being
benefited through this shop. The employees are getting salary as per the month. The
employees are given bonus during festival of every year.

Already there was no computerization was started. The main transactions involved in
this computer and software development. They give good products to the customers.

Since the existing system is a manual one, lot of paper work and manpower are
needed. With the existing system, a large number of ledgers, papers, records, etc have to be
kept for future use. And this consumes a large amount of office space.

Searching and finding a particular detail of a customer from a large number of records
needs a large amount of time. Also the data can be lost in future.

3
 CHAPTER-II

SYSTEM STUDY

2.1 EXISTING SYSTEM

The project entitled “Tiles showroom Management System” is developed to

minimize the burden of agent who maintain the details manually and give necessary report to
the user needed minimize the abnormal time consumption. In the main drawback is the user
want to find a particular tiles purchase details, then the user has to check all the ledgers and it
will takes a long time. At the same time the ledgers are damaged after a particular period. in
addition to this retrieval is also very difficult one.

The existing system study is done at the “TILES SHOWROOM MANAGEMENT

SYSTEM” here all the transactions are done manually. Manual performance of these
functions causes a large wastage of time and manpower the major transaction such as
purchase and sales entries are done manually. All these transaction in the existing system
wastes lot of office space, numbers of employees increase, searching for a particular
customer details requires searching in a number of records or books and also across due to
human calculation also come. All these drawbacks prompted to develop a computerized
system that avoids all the disadvantages or drawbacks of the existing system.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

 In the existing system tiles purchase and sales process manually.
 It will take a huge time and human errors will occur in this type of manual work.
 For maintaining all these ledgers in a computerized way it is very easy to maintain
and the manpower will also be reduced.
 It is very helpful to the organization.
 Calculation does not more accuracy.
 Daily sales information report does not maintained properly.

4
2.2 PROPOSED SYSTEM
The main aim of this system is to reduce manual work and this computerized system
saves time and provides up to date information day to today. It requires a lot of time spared in
waiting detail in the tiles and reports. It also requires large space to store valuable records.

The proposed system aims to provide solutions to the observed draebacks in the exiting
system. The proposed system provides the solution for the purchase detail, employee details,
customer details, delivery details, sales details, salary for working employee details and the
problems in customized report generation. This proposed system also gives the user an
interactive, easy to use interface which reduces his burden to enter the process details

2.3 FEATURES OF THE PROPOSED SYSTEM

 Immediate retrieval at records in the file during update runs.
 Current statement of the files is available.
 Data security is provided using password.
 System for process is very fast compared to existing system.
 Event driven programming is provided using menus.
 Reports are quickly available to the user.
 Error in calculations can be easily eliminated.
 Completely menu driven and user friendly.
 Provides faster and efficient information processing.
 Supports efficient data management.
 Highly flexible.
 Valid and secure.
 Provides timely information.
 Tiles purchase stock and sales information daily updated very well.

5
 CHAPTER - III

SYSTEM SPECIFICATION

3.1 SYSTEM SPECIFICATION

3.1.1 HARDWARE SPECIFICATION

MONITOR : LCD MONITOR 15” COLOR

PROCESSOR : INTEL PENTIUM 4

HARD DISK : 560GB

MOUSE : OPTICAL MOUSE

KEYBOARD : 104 KEYS

RAM : 4 GB

3.1.2 SOFTWARE SPECIFICATION

OPERATING SYSTEM : MICROSOFT 10

FRONT-END : VISUAL BASIC 6.0

BACK-END : MS-ACCESS 2007

6
3.2 AN OVERVIEW OF SOFTWARE

3.2.1 VISUAL BASIC 6.0

Visual Studio is a complete set of development tools for building .

 VB Web.
 Applications XML
 Web services
 Desktop applications.
 mobile applications

Visual Basic , Visual C ++ , and Visual C # all use the same integrated
development environment ( IDE ) , which allows them to share tools and
facilitates in the creation of mixed language solutions .

Visual Basic Visual Basic has been updated to include many new and improved
language features that make it a powerful object - oriented programming
language.

These features include inheritance, interfaces, and overloading, among others.

Visual Basic also now supports structured exception handling, and custom
attributes. In addition, Visual Basic supports multithreading. Multithreading is
the ability to assign individual tasks to separate processing threads.

Visual Basic, as a new programming language that is an evolution of GUI

providing a simple and type - safe language for developing applications . Visual
basic has been updated to be a class - based, language that maintains full
backwards compatibility with previous versions of VB . It provides class -
based objects , typed variables , true compiled code , and cross - language
support through Common Language Specification ( CLS ) compliance . The
primary role of VB is development of Web sites with VB and customization of
applications with Script for the Framework .

7
Types of forms used in Visual Basic

Web Forms

Web Forms are anVB technology that you use to create programmable Web
pages. Web Forms render themselves as browser compatible HTML and script ,
which allows any browser on any platform to view the pages Using Web Forms
you create Web pages by dragging and dropping controls onto the designer and
then adding code , similar to the way that you create Visual Basic forms

Windows Forms

Windows Forms is the new platform for Microsoft Windows application

development, based on the Framework.

This framework provides a clear, GUI, extensible set of classes that enables
you to develop rich Windows applications. Additionally, Windows Forms can
act as the local user interface in a multi - tier distributed solution.

The visual basic is a new computing platform that simplifies application

development in the highly distributed environment of the Internet.

It is designed to fulfill the following objectives .

 To provide a consistent programming environment whether object code is

stored and executed locally, executed locally but Internet - distributed , or
executed remotely .
 To provide a code - execution environment that minimizes software
deployment and versioning conflicts . .
 To provide a code - execution environment that guarantees safe execution
of code , including code created by an unknown or semi - trusted third
party .
 To provide a code - execution environment that eliminates the
performance problems of scripted or interpreted environments .
 To make the developer experience consistent across widely varying types
of applications , such as Windows - based applications and Web - based
applications . To build all communication on industry standards to ensure
that code based on the Framework can integrate with any other code .

8
DESIGNING, TESTING AND EXECUTING PROGRAMS

An Integrated Development Environment (IDE) such as the VB 6.0

environment allows users to :

• Design
 Test
• Execute or Run

Their programs through an integrated system. Thus, the development of VB

programs goes through three phases. Developers first design programs by
designing the Form , selecting appropriate controls if necessary and specifying
what code should execute when a particular event takes place .

The code associated with an event is typed in by selecting the view code tab in
the Project Explorer Window or by double clicking the Form in the Form
Window. The view can be switched back to Form by click in go the view object
tab in the Project Explorer Window .

While viewing code by clicking on the view code . tab in the Project Explorer ,
one can choose between ( General ) and ( Form ) through a dropdown menu .
All events associated with a Form can be selected by clicking on the Form drop
down menu on the top left of the Form in code view .

VB Code is written in a block in between the Private Sub and End Sub
keywords. The corresponding event that triggers this particular block of
instructions is identified by the title of the event such as Form_Load ,
Form_Click , Form_Dbl_Click etc.

Once code has been written , the program can be executed or run by clicking on
the Start button onthe Toolbar .

Notice that the menu title of the Form changes from Project - Microsoft Visual
Basic design to Project1 - Microsoft Visual Basic run As soon as the program
begins execution . In the run mode , the application executes theapplication
program and behaves as instructed during the design mode .

9
Common Language Runtime .

Despite its name , the runtime actually has a role in both a component's
runtime and development time experiences . While the component is running ,
the runtime is responsible for managing memory allocation , starting up and
stopping errors and processes , and enforcing security policy , as well as
satisfying any dependencies that the component might have on other
components . At development time , the runtime's role changes slightly ;
because it automates so much ( for example , memory management ) , the
runtime makes the developer's experience very simple , especially when
compared to COM as it is today . In particular , features such as reflection
dramatically reduce the amount of code a developer must write in order to turn
business logic into a reusable component .

Unified programming classes

The framework provides developers with a unified, hierarchical, and

extensible set of methods. Currently, VB developers use the Microsoft
Foundation developers use the Windows Foundation Classes. The framework
unifies these disparate models and gives Visual Basic programmer's access to
libraries as well. By creating a common set of APIs across all programming
languages, the common language runtime enables cross - language inheritance,
error handling, and debugging. All programming languages, from VB, have
similar access to the framework and developers are free to choose the language
that they want to use.

VB builds on the programming classes of the Framework, providing a Web

application model with a set of controls and infrastructure that make it simple to
build VB Web applications. VB includes a set of controls that encapsulate
common HTML user interface elements, such as text boxes and drop - down
menus. These controls run on the Web server, however, and push their user
interface as HTML to the browser. On the server , the controls expose an object
oriented programming model that brings the richness of object oriented
programming to the Web developer VB also provides infrastructure services ,
such as session state management and process recycling that further reduce the
amount of code a developer must write and increase application reliability . In
addition, VB uses these same concepts to enable developers to deliver software
as a service.

10
Debugging

Visual Studio provides a single integrated debugger for all Visual Studio
languages. including Visual Basic and C # . A new , unified interface combines
features of the Visual C ++ and Visual Basic 6.0 debuggers , as well as many
new features .

Cross Language Debugging

Using the integrated debugger , you can debug projects that are part of the
same solution but are written in different languages . For example , you can
debug a solution that contains a project consisting of a Visual Basic user
interface application and a Visual Basic server application , and you can step
back and forth between these projects , for example from Managed Extensions
for C ++ to Visual Basic and back to Managed Extensions for C ++ .

Attaching to a Running Program

VB can attach the debugger to a program that is already running and debug
the program . Attaching to a running program works the same way whether the
program is running on a host machine or a remote machine . The program does
not need to be launched in the Visual Studio integrated development
environment ( IDE )

Remote Debugging

VB can attach to and debug a process that is running on a different computer

from the one on which you are running Visual Studio . For example , if you are
debugging a Windows Forms client application and an XML Web service it
uses , you can run Visual Studio on the client and then attach to the server that
is providing the XML Web service . You typically perform this kind of
debugging for Web Forms projects or VB Web Service projects .

Debugging Multiprogramming Applications

New for Visual Basic users is the ability to write and debug
multiprogramming applications. The Threads window can be used to view the
errors that are running and to switch context.

11
Debugging Multiple Programs

VB can debug multiple programs by attaching to running programs or by

launching multiple programs from the Visual Studio IDE .

3.2.2 MS - ACCESS

FEATURES OF MS-ACCESS 2007

Microsoft Access 2007is a powerful, yet easy to learn, relational database

application for Microsoft Windows. This tutorial is designed for users who are
new or only have little experience using Access 2007.

It introduces fundamental database concepts and operations and illustrates

how they are performed in Microsoft Access 2007. This tutorial does not cover
all of the features and functions of Microsoft Access 2007 emphasis will be on
basic and frequently - used features , such as the creation of tables and queries ,
or importing spreadsheet into Access . It is only available for Windows users ;
Mac users may want to seek out a FileMaker Pro Tutorial .

Objectives

• Launch Access and identify the parts of the screen .

• Define fields and field properties constructing table structures.

• Enter and edit records in a table.

• Find, sort data . .

• Design custom queries to display data .

• Import and export data between Excel and Access .

Definitions

These words are used often in Access so you will want to become familiar with
them before using the program and this tutorial .

12
Relational Database

In relational databases such as Access , data is stored in tables made up of

one or more fields ( Access calls a column a field ) . The data stored in each
column must be of a single data type such as Character , Number or Date . A
collection of values from each column of a table is called a record or a row in
the table . Different tables can have the same column in common . This feature
is used to explicitly specify a relationship between two tables . Values
appearing in column A in one table are shared with another table

Table

Tables are the main units of data storage in a database . A table is a collection
of data about a specific topic ; it is made up of one of more fields .

Field A field is a column in a table and defines a data type for a set of values in
a table . For example , a mailing list table might include fields for first name ,
last name , address , city , state , zip code , and telephone number .

Record A record in a row in a table and is a set of values defined by fields . In a

mailing list table , each record would contain the data for one person as
specified by the intersecting fields .

Data type Data types are the properties of each field . A field only has one data
type , such as Character , Number or Date .

Primary Key A primary key is a value that can be used to identify a unique
record in a table .

Design View It provides the tools for creating fields in a table .

Datasheet View It allows you to update , edit , and delete information from a
table

MS - Access is a database management system ( DBMS ) Like other items in

the category , Access stores and retrieves data , presents information and
automates repetitive tasks ( such as maintaining accounts payable , inventory
control and scheduling ) . Access is also a powerful windows application .

13
 CHAPTER-IV

SYSTEM DESIGN AND DEVELOPEMENT

.

4.1 FILE DESIGN

The design of the system is essentially a blue print or plan for solution of the
System to be developed. A part of the system or sub system of a whole system can itself be
considered a system with its own complements

The file deign is the last phase that indicates the final system and process of the
final system. In the design phase of „TILES SHOWROOM MANAGEMENT SYSTEM‟,
the database tables, input screen design and output design etc., are designed.

 The database tables were designed by using all the necessary fields in compact
manner.
 All the input screens in this system are user-friendly and understandable format. Also
the sizes of all the screens are standardized.
 Icons designed in this system are brief, compact and self-explanatory. The icons are
sharp and the user can invoke the system.
 Reports generated here give the minute information, which helps the manager to take
vital decisions.

The importance of software design can be stated with a single word “QUALITY”.

Design is a place where quality is fostered in software development. Design is the

only way where their requirements are accurately translated into finished software product or
system.

14
4.2 INPUT DESIGN
Input design is the process of converting user-originated inputs to a computer-
based format. The system takes input from the users, processes it and produces an output.
Input design is link that ties the information system into the world of its user. The system
should be users friendly to gain appropriate information to the user.

Forms for input design in this project are:

 Purchase Details
 Sales Details
 Delivery Details
 Employee Details
 Customer Details

4.3 OUTPIT DESIGN

Output design generally refers to the results and information that are integrated 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 the application.

The objective of a system finds its shape in terms of output; Output of a system can
face various forms. The most command are the reports, screen displays, printed forms,
graphical, drawings etc. The basic requirements of output are that, it should be accurate,
timely and of content, medium and layout for its in tented purpose.

External output are those whose destination will be outside the organization.
Interactive outputs are those, in those, in which user uses in communicating directly with
computer.

This report given in this project are:

 Purchase Report
 Sales Report
 Employee Report
 Customer Report
 Delivery Report

15
4.4 DATABASE DESIGN

The database management system (DBMS) consists of a collection of interrelated

data and a set of programs to access their data. The collection of data usually referred to as
database. The primary key goal of DBMS is to provide an environment that is both
convenient and efficient to use in retrieving and storing data information.

The term database design can be used to describe many different parts of the design of
an overall database system. Principally and most correctly, it can be through of as the logical
design of the data structure used to store the data. In the relational model these are the tables
and vies. In an object database the entities and relationships map directly to object classes and
named relationships. However, the term database design could also be used o apply to the
overall process of designing, not just the base data structures, but also the forms and queries
used as part of the overall database application within the database management
system(DBMS).

The process of doing database design generally consists of a number of steps which
will be carried out by the database designer.

16
4.5 SYSTEM DEVELOPMENT
A system development project encompasses all the activities undertaken from the
time at which a potential requirement is identified until the resulting system is fully
implemented and accepted by the end user. The process can involve many stages over a long
period. The following section highlights some fundamental issues to be considered, outlines
the main stages in development and procuring new system and indicates when and how the
auditor should be involved.

An information system acquired today must not only satisfy present business
needs; it must also be flexible and capable of being enhanced to meet changing circumstances
well into the future. Thus a pre-requisite to the introduction of a new system is for
management to identify and understand their organisation’s mission and its related
information needs. Writing this down helps to ensure common understanding and direction
and provides a yardstick against which achievement can be measured.

The first step in which the analyst must undertake is to understand the current
system by gathering all information about it. The required data are collected by several
methods like:

 Study of the current manuals

 Observation of the functioning
 Sampling and research

17
4.5.1 DESCRIPTION OF MODULES

MASTER MODULE
It will store and maintain the details of purchase details, employee details, customer
details entire information.

Purchase details
To store the customer name, item no, total amount, purchase date, phone number,
address.

Employee details
To store the employee name, employee id, address, phone number, email id, age and
sex, designation, salary, date of join.

Customer details
To store the customer name, item no, address, phone number, amount, email id, date.

TRANSACTION MODULE
It can be used to maintain the delivery details, sales details.

Delivery details
This modules is used to store the customer name, item no, address, phone number,
amount.

Sales details
This modules is used to store the customer name, item no, sales amount, sales date, phone
number, address.

VIEW MODULES
It can be used to maintain the purchase details, delivery details, customer details.

Purchase details
This modules is used to store the customer name, item no, total amount, purchase date,
phone number, address.

18
Delivery details
This modules is used to store the customer name, item no, address, phone number,
amount.

Customer details
This modules is used to store the customer name, item no, address, phone number, amount,
email id, date.

REPORT MODULE
This report will generate automatically. This is maintained and calculated accurately.
This reports are displayed in neat formats. The delivery, sales, purchase, employee, customer
details will have a separate report.

Delivery report
It is used to view the details about the delivery of the tiles system. For example to
store the customer name, item no, address, phone number, amount.

Sales report
It is used to view the details about the sales of the tiles system. for example to store the
customer name, item no, sales amount, sales date, phone number, address.

Purchase report
It is used to view the details about the purchase tiles. For example to store the customer
name, item no, total amount, purchase date, phone number, address.

Employee report
It is used to view the details about the employee tiles to the system. For example to
store the employee name, employee id, address, phone number, email id, age and sex,
designation, salary, date of join.

Customer report
it is used to view the store the details about the customer to the tiles. For example to
store the customer name, Item no, address, phone number, amount, email id, date.

19
 CHAPTER-V

SYSTEM TESTING & IMPLEMENTATION

5.1 SYSTEM TESTING

All the modules of this system were successfully implemented and testing of the
project completed using test data as well as real data collected from the office. All the reports
correctness and consistency. After successful testing of the system, it was ready for
implementation.

Unit testing
In this testing, we have to test the programs making up the system. The software units
in a system are the modules and routines that are assembled and integrated to perform a
specific function. Unit testing focuses first on the modules, independently of one another, to
locate errors. This enables, to detect errors in coding and logic that are contained within that
module alone.

Integration testing
The constituents of the entire project are split into individual module and were linked
together, and until the maximum level for each transaction type was reach. This module have
its individual programs, these programs were tested individually. At last all these programs
were combined together.

Validation testing
At the culmination of integration testing software is assembled as a package interface
errors have been uncovered and corrected and a final series tests validation test begin.
Validation testing can be defined in many ways, but a simple definition is that validation
succeeds when the software functions in a manner that can be reasonably expected by the
customer. After validation test has been conducted, one of two possible conditions exits.

Security testing
During this testing, the tester plays the role of the individual who desires to penetrate
the system. The tester may also over when the system there by denying service to others.

White box testing

It is a test case design method that uses the control structure of the procedural design
to derive test cases, using white box test method. Guarantee that all independent paths with
in a module have been exercised at least one. Exercise all logical decision on their true and
false sides. Execute all loops at their boundaries and within their operational bounds.

20
Black box testing
It is not an alternative to white box techniques. It is attempts to find errors in the
following categories. Incorrect or missing functions interface errors. Errors in data as
structures or external database access. Performance errors.

5.2 SYSTEM IMPLEMENTATION

The designed system must be implemented to fulfil development. There are many
software implementation methods. In this system direct change over from existing system to
computer is carried out.

After a system design is over, the user was consulted with a demonstration. This
was done to find if any logical error occur in the system. Since the complete system has been
developed according to user requirements, the demonstration is necessary. Various
combinations of test the system accuracy and reliability.

This implementation plans involve planning, investigation of the current system

and its constraints on implementation, design of methods to achieve the change over and
evaluation to change over method.

21
 CHAPTER-VI

CONCLUSION
This project report entitled of “TILES SHOWROOM MANAGEMENT
SYSTEM” is more efficient than the existing system. This system provides some additional
information regarding the employee salary depend on the leave and attendance using tiles
concept. Information can be stored and retrieved with accuracy and error-free. The sharing of
information at department level is well established. So the information is shared whenever
the departments require it.

By providing access level to authorised persons. Security of accessing

information from the database is well implemented. The system will not allow all the users to
access all information from database. Only a particular user can be provide with all
information all other is limited in access the information. The reports for both the
departments are generated based on the requirements of user. Since change is a way of life
new requirements may arise in future

These projects are generated based on the requirements of the department.

Generally Reports can be downloaded in excel sheet only. So whenever there is a need for
generating any type of report, then it is possible by using the system.

22
SUGGESTIONS
The system has satisfied all the requirement of the user, there is further scope
of moulding this system in to a better form in the following areas as follows:

 Insurances for employees.

 Loan facilities module for employees to be added.

These are some of the key areas where the system can be developed future.

FUTURE ENHANCEMENTS
Any project which is done is having room for development. It can be enhanced
with various options according to the customer satisfaction in future, as far as “Tiles
Showroom Management System” is concerned, we can enhance it with various options like
having a new module regarding the transaction of sales details.

It can also have an inbuilt module to completely manage the agent order and
sales of the employees. That is it can have a purchase module with this for depends upon the
agent order and calculation. All the details regarding transaction can be added to this with
valuable report generation.

Every application has its own merits and demerits. The project has covered
almost all the requirements. Future requirements and improvements can easily be done since
the coding is mainly structured or modular in nature. Changing the existing modules or
adding new modules can append improvements.

The application become useful if the bellow enhancements are made in future.

 The application if developed as website, can be used from anywhere.

 Repeated services to selected customers details can be maintained.
 New offered will be automatically send to the customer mail via
short message service (sms).

The application is designed such those enhancements can be integrated with

current modules easily with less integration work.

23
 BIBLOGRAPHY

BOOK REFERENCE:

1. Elias M.Awad, “system analysis and design”, Galgotia Publications (p) Ltd,
Second Edition, 1996.
2. Gary Cornell, “visual basic 6.0”, Tata Mc Gary-Hill Publications, Fourth Edition,
1999.
3. Naveen Prakash, “Introduction To Database Management System” Tata Mc
Graw Hill Publication , 1995.
4. Roger Pressman, “Software engineering”, Tata Mc Graw – Hill Publications,
Fourth Edition, 1994.
5. Silberschatz, korth, sudharsan, “Database System concept”, Tata McGraw-
Hill, First Edition, 2002.

URL REFERENCE:
 http://www.vb6.us/tutorials/access-and-visual-basic-using-ado
 http://download.access.com/docs/html/B10952-01/o4o00069.Access
 http:/Visualbasicnetblogspot.com/2011/03/connect-access-database-usingvisual.

24
 APPENDIX

A)DATAFLOW DIAGRAM

TRANSACTION
MASTER

PURCHASE DETAILS MDI FORM

DELIVERY DETAILS

EMPLOYEE DETAILS

SALES DETAILS

CUSTOMER DETAIL

DELIVERY DETAILS

PURCHASE DETAILS
SALES DETAILS

DELIVERY DETAILS
PURCHASE DETAILS

CUSTOMER DETAILS EXIT EMPLOYEE DETAILS

VIEW CUSTOMER DETAILS

REPORT

25
B) TABLE STRUCTURE

Table name : Purchase details

Purpose : This table is used to store the purchase details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Customer name Text 15 Primary key Customer name

Item no Number 5 Not Null Item no

Total amount Number 15 Not Null Total amount

Purchase date Date & time 10 Not Null Purchase date

Phone number Number 10 Not Null Phone number

Address Text 25 Not Null Address

Table Name : Sales details

Purpose : This is used to store the various sales details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Customer name Text 15 Foreign key Customer name

Item no Number 5 Not Null Item no

Sales amount Number 15 Not Null Sales amount

Sales date Date & time 10 Not Null Sales date

Phone number Number 10 Not Null Phone number

Address Text 25 Not Null Address

26
Table Name : Delivery details

Purpose : This is used to store the various delivery details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Customer name Text 15 Primary key Customer name

Item no Number 6 Not Null Item no

Address Text 25 Not Null Address

Phone number Number 10 Not Null Phone number

Amount Number 15 Not Null Amount

27
Table Name : Employee details

Purpose : This is used to store the various employee details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Employee name Text 6 Foreign key Employee name

Employee id Number 5 Not Null Employee id

Address Text 25 Not Null Address

Phone number Number 10 Not Null Phone number

Email id Text 18 Not Null Email id

Age and Sex Text 19 Not Null Age and sex

Designation Text 20 Not Null Designation

Salary Number 10 Not Null Salary

Date of join Date & time 10 Not Null Date of join

28
Table Name : customer details

Purpose : This is used to store the various customer details.

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

Customer name Text 15 Primary key Customer name

Item no Number 10 Not Null Item no

Address Text 25 Not Null Address

Phone number Number 10 Not Null Phone number

Amount Number 10 Not Null Amount

Email id Text 15 Not Null Email id

Date Date & time 10 Not Null Date

29
C) SAMPLE CODING

Dim db As New ADODB.Connection

Dim EM As New ADODB.Recordset

Private Sub Command1_Click() 'new

Call CLEAR

Text1.SetFocus

MsgBox "please type the data"

If EM.BOF Then

Text1.Text = 1

Else

EM.MoveLast

Text1.Text = Val(EM(0)) + 1

End If

Text2.SetFocus

End Sub

Private Sub Command10_Click() 'mnext

EM.MoveNext

Call view

End Sub

Private Sub Command11_Click() 'mpre

EM.MovePrevious

Call view

End Sub

30
Private Sub Command12_Click() 'mlast

EM.MoveLast

Call view

End Sub

Private Sub Command2_Click() 'save

Call SAVE

Call CLEAR

Text1.SetFocus

If EM.BOF Then

Combo1.Text = 1

Else

EM.MoveLast

Text1.Text = Val(EM(0)) + 1

End If

Text2.SetFocus

End Sub

Private Sub Command3_Click() 'clear

Call CLEAR

End Sub

Private Sub Command4_Click()

End

End Sub

Private Sub Command5_Click() 'modify

MsgBox ("ARE YOU WANT TO MODIFY")

31
r = InputBox("ENTER THE NO:")

If Trim(r) = "" Then

MsgBox ("PLEASE GIVE NO")

Exit Sub

End If

EM.MoveFirst

While Not EM.EOF

If UCase(Trim(r)) = UCase(Trim(EM(0))) Then

Call DISPLAY

Exit Sub

End If

EM.MoveNext

Wend

MsgBox ("PLEASE VERIFY THE NO")

End Sub

Private Sub Command6_Click() 'update

EM(0) = Text1.Text

EM(1) = Text2.Text

EM(2) = Combo1.Text

EM(3) = DTPicker1

EM(4) = Combo2.Text

EM(5) = Combo3.Text

EM(6) = Combo4.Text

EM(7) = DTPicker2

32
EM(8) = Text3.Text

EM(9) = Text4.Text

EM(10) = Text5.Text

EM(11) = Text6.Text

EM.Update

MsgBox "updated"

Call CLEAR

If EM.BOF Then

Text1.Text = 1

Else

EM.MoveLast

Text1.Text = Val(EM(0)) + 1

End If

End Sub

Private Sub Command7_Click() 'DEL

MsgBox ("ARE YOU WANT TO DELETE")

r = InputBox("ENTER THE NO:")

If Trim(r) = "" Then

MsgBox ("PLEASE GIVE NO")

Exit Sub

End If

EM.MoveFirst

While Not EM.EOF

If UCase(Trim(r)) = UCase(Trim(EM(0))) Then

33
Call DISPLAY

EM.Delete

MsgBox ("RECORD DELETED")

Call CLEAR

Exit Sub

End If

EM.MoveNext

Wend

MsgBox ("PLEASE VERIFY")

If EM.BOF Then

Text1.Text = 1

Else

EM.MoveLast

Text1.Text = Val(EM(0)) + 1

End If

End Sub

Private Sub Command8_Click() 'SEARCH

MsgBox ("ARE YOU WANT TO SEARCH")

r = InputBox("ENTER THE NO:")

If Trim(r) = "" Then

MsgBox ("PLEASE GIVE NO")

Exit Sub

End If

EM.MoveFirst

34
While Not EM.EOF

If UCase(Trim(r)) = UCase(Trim(EM(0))) Then

Call DISPLAY

Exit Sub

End If

EM.MoveNext

Wend

MsgBox ("PLEASE VERIFY THE NO")

End Sub

Private Sub Command9_Click() 'mfirst

EM.MoveFirst

Call view

End Sub

Public Sub SAVE()

pc.AddNew

pc(0) = Text1.Text

pc(1) = Text2.Text

pc(2) = Combo1.Text

pc(3) = Text3.Text

pc(4) = Text4.Text

pc(5) = Combo2.Text

pc(6) = Text5.Text

pc(7) = Text6.Text

pc(8) = Text7.Text

35
pc(9) = Text8.Text

pc(10) = Text9.Text

pc(11) = Text11.Text

pc(12) = Text12.Text

pc.Update

MsgBox "data stored"

End Sub

Public Sub DISPLAY() 'USE MODIFY UPDATE, DEL

Text1 = pc(0)

Text2 = pc(1)

Combo1 = pc(2)

Text3 = pc(3)

Text4 = pc(4)

Combo2 = pc(5)

Text5 = pc(6)

Text6 = pc(7)

Text7 = pc(8)

Text8 = pc(9)

Text9 = pc(10)

'Text10 = pc(11)

Text11 = pc(11)

Text12 = pc(12)

End Sub

Public Sub view() 'USE ALL MOVE FIR, NEXT, PRE, LAST

36
If pc.BOF = True Then

pc.MoveFirst

ElseIf pc.EOF = True Then

pc.MoveLast

End If

Text1 = pc(0)

Text2 = pc(1)

Combo1 = pc(2)

Text3 = pc(3)

Text4 = pc(4)

Combo2 = pc(5)

Text5 = pc(6)

Text6 = pc(7)

Text7 = pc(8)

Text8 = pc(9)

Text9 = pc(10)

'Text10 = pc(11)

Text11 = pc(11)

Text12 = pc(12)

End Sub

Private Sub Text11_GOTFocus()

Text11 = Val(Text9) * (Val(Text10) / 100)

End Sub

Private Sub Text12_GotFocus()

37
Text12.Text = Val(Text9.Text) - (Text11.Text)

End Sub

Private Sub text9_GotFocus()

Text9.Text = Val(Text7.Text) * Val(Text8.Text)

End Sub

38
A) SAMPLE OUTPUT

39
MASTER MENU

40
PURCHASE DETAIL

41
EMPLOYEE DETAIL

42
CUSTOMER DETAIL

43
TRANSACTION MENU

44
SALES DETAIL

45
VIEW MENU

46
PURCHASE DETAIL

47
CUSTOMER DETAIL

48
REPORT MENU

49
DELIVERY REPORT

50
SALES REPORT

51
PURCHASE REPORT

52
EMPLOYEE REPORT

53
CUSTOMER REPORT

54