INTRODUCTION

This project is aimed to develop the “PROVISION STORE

MANAGEMENT” Administration System which is used to simplify the
Maintenance of the complete details of products, inventory, customers, billing,
delivery of goods etc. This project is a widely used in many big “PROVISION
STORE MANAGEMENT” and is used to cater the need of the sales system
there. This is a system that is used to maintain / control most of the activities
happening in PROVISION STORE MANAGEMENT. This maintains and
controls the stock details and does billing and generates various Reports.

1
 OBJECTIVES AND SCOPE OF PROJECT

Objective:-

 The main objective of the project is to help the project is to help the ongoing
user help to attain an easy way to navigate the customer’s details and solve
the customer’s problems.
 It is basically a very instant processing system by which customer can get
the book in the right condition.
 The manager of the book store also finds it sufficient enough to view the
details of the sales, servicing and well organized way to employ the staff that
are included in the book store staff.

Scope:-

 The project could be implemented in an average sized organization.

 An average company will not be very keep on spending loads of money on
ledgers whereas that project will greatly reduce the costs which is using
common and cheap office items like database and desktop application.
 And also there is no requirement to store books or accounts. The data is
directly stored in the database in the hard disk of the PC.

2
 THEORETICAL BACKGROUND OF PROJECT:-

The software entitled “PROVISION STORE MANAGEMENT” is made for

book for handling near about all tasks as mentioned in the objectives phase. This
software has the facilities for the “PROVISION STORE MANAGEMENT” to
perform their work easily and safely. This software has used friendly Graphical
User Interface that makes easy to handle data of the book shop. Using this software
book shop can easily maintain there from basic to higher level problems. These
tasks can include:

1. Keep the MANAGEMENT record for every customer.

2. Daily transaction record should be kept for every customer and book.
3. Only authorized users can login through giving login password.
4. Only the developer can change user name and password if he wants.

3
 DEFINATION OF PROBLEM

1. Problem of Reliability: Current system is not reliable. It seems to vary in

quality from one month to the next. Sometimes it gives good output, but
sometimes the output is worst.
2. Problem of Accuracy: There are too many mistakes in reports.

3. Problem of timeliness: In the current system the reports and output produced is
mostly late and in most of the cases it is useless because it is not on time.

4. Problem of Validity: The output and reports mostly contains misleading

information. The information is sometimes not valid.

5. Problem of Economy: The current system is very costly. We have to spend lots
of money to keep the system up and going, but still not get the desired results.

6. Problem of Capacity: The current system is suffering from problem of

capacity also. The staff for organization is very less and the workload is too
much. Few peoples cannot handle all the work.

4
 SYSTEM ANALYSIS AND DESIGN

SYSTEM ANALYSIS

System analysis is the process of gathering and interpreting facts, diagnosing

problems and using the information to recommend improvements on the system.
System analysis is a problem solving activity that requires intensive
communication between the system users and system developers.
System analysis or study is an important phase of any system development
process. The system is studied to the minutest detail and analyzed. The system
analyst plays the role of an interrogator and dwells deep into the working of the
present system. The system is viewed as a whole and the inputs to the system are
identified. The outputs from the organization are traced through the various
processing that the inputs phase through in the organization.
A detailed study of these processes must be made by various techniques like
Interviews, Questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of how
the system functions. This system is called the existing system. Now, the existing
system is subjected to close study and the problem areas are identified. The
designer now functions as a problem solver and tries to sort out the difficulties that
the enterprise faces. The solutions are given as a proposal. The proposal is then
weighed with the existing system analytically and the best one is selected. The
proposal is presented to the user for an endorsement by the user. The proposal is
reviewed on user request and suitable changes are made. This loop ends as soon as
the user is satisfied with the proposal.

Existing system

The current system is a computerized but which is maintained at individual

database .the system doesn‘t provide complete services like reports, and
centralized database.

5
Limitation in Existing system

1. This system is maintained at individual database.

2. The user or customer at individual database.
3. In the current system there is not much database maintenance,
therefore accessing single records take more time to verify the data of
particular customer information.
4. Customer doesn’t have any permission to access their own accounts.

Proposed system

The proposed system is a browser which is completely related to system,

which provides the centralized data base. The system allows
multidivisional, multi-department system handing that includes various
activities.

Advantages over Existing system

 In this system the data base is maintained in centralized manner.

 This system is very fast because of the centralized data base and accessing
data base will be very easy, when compared to existing system.

6
 SOFTWARE DESIGN

Design considerations

There are many aspects to consider in the design of a piece of software. The
importance of each should reflect the goals the software is trying to achieve. Some
of these aspects are:

 Compatibility -The software is able to operate with other products that are
designed for interoperability with another product. For example, a piece of
software may be backward-compatible with an older version of itself.
 Extensibility – New capabilities can be added to the software without major
changes to the underlying architecture.
 Fault-tolerance –The software is resistant to and able to recover from
component failure.
 Maintainability –The software can be restored to a specified condition
within a specified period of time. For example, antivirus software may
include the ability to periodically receive virus definition updates in order to
maintain the software’s effectiveness.
 Modularity – The resulting software comprises well defined, independent
components. That leads to better maintainability. The components could be
then implemented and tested in isolation before being integrated to form a
desired software system. This allows division of work in a software
development project.
 Packaging- Printed material such as the box and manuals should match the
style designated for the target market and should enhance usability. All
compatibility information should be visible on the outside of the package.
All components required for use should be included in the package or
specified as a requirement on the outside of the package.
 Reliability- The software is able to perform a required function under stated
conditions for a specified period of time.
 Reusability- The modular components designed should capture the essence
of the functionality expected out of them and no more or less. This single-
minded purpose renders the components reusable wherever there are similar
needs in other designs.

7
  Robustness- The software is able to operate under stress or tolerate
unpredictable or invalid input. For example, it can be designed with
resilience to low memory conditions.
 Security- The software is able to withstand hostile acts and influences.
 Usability- The software user interface must be intuitive (and often
aesthetically pleasing) to its target user/audience. In many cases, online help
should be included and also carefully designed.

Modeling language:-

A modeling language is an artificial language that can be used to

express information or knowledge or systems in a structure that is defined by a
consistent set of rules. The rules are used for interpretation of the meaning of
components in the structure. A modeling language can be graphical or textual.

SOFTWARE REQUIREMENT SPECIFICATION

INTRODUCTION:-

8
 Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation and
for determining the operating characteristics of the system.

Scope: This document plays a vital role in the development life cycle (SDLC) as it
describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirement in the future will have to go through formal change approval process.

Functional Requirements:

OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the

results of processing to users. They are also used to provide a permanent copy of
the results for later consultation. The various types of outputs in general are:

 External outputs, whose destination is outside the organization,

 Internal Outputs whose destination is with in organization and they are the
user’s main interface with the computer.
 Operational Outputs whose use is purely with in the computer department.
 Operational outputs, which involve the user in communicating directly with.

Output Definition

The outputs should be defined in terms of the following points:

 Type of the output.

 Content of the output.
 Format of the output.
 Location of the output.
 Frequency of the output
 Volume of the output
 Sequence of the output

It is not always desirable to print or display data as it is help on a computer. It

should be decided as which from of the output the most suitable is.

9
 INPUT DESIGN

Input design is a part of overall system design. The main objective during the input
designing is as given below:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the
user.

INPUT STAGES:

The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be categorized

as follows:

 External inputs, which are prime inputs for the system.

 Internal inputs, which are user communications with the
system.
 Operational, which are computer department’s communications
to the system.
 Interactive, which are inputs entered during a dialogue.
DATABASE DESIGN
The general theme behind a database is to handle information as
an integrated whole System. A database is a collection of interrelated data
stored with minimum redundancy to serve many users quickly and effectively.
After designing input and output, the analyst must concentrate on database
10
 design or how data should be organized around user requirements. The general
objective is to make information access, easy quick, inexpensive and flexible
for other users. During database design the following objectives are concerned:-

 Controlled Redundancy
 Data independence
 Accurate and integrating
 More information at low cost
 Recovery from failure
 Privacy and security
 Performance
 Ease of learning and use

Performance requirements:

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only

when the requirement specifications are properly given, it is possible to design a
system, which will fit into required environment. It rests largely in the part of the
users of the existing system to give the Requirement specification because they are
the people who finally use the system. This is because the requirements have to be
known during the initial stages so that the system can be designed according to
those requirements. It is very difficult to change the system once it has been
designed and on the other hand designing a system, which dies not cater to the
requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given
below:

 The system should be able to interface with the existing system

the existing system
 The system should be accurate
 The system should be better then the existing system

The requirement specification for any system can be broadly stated as given below:

 The system should be able to interface with the existing the

existing system

11
  The system should be accurate
 The system should be better then the existing system

The existing system is completely dependent on the staff to perform all the
duties.

12
DETAILS OF HARDWARE AND SOFTWARE REQUIREMENT

1. SOFTWARE

 Platform - Visual Basic 6.0

 Database – MS Access 2003
 Technology - MS ActiveX object 2.0 Library & MS data binding
Collection 6.0
 Best performance - Windows XP.

2. HARDWARE

 Processor - Pentium 80486 or 80486 Above

 Ram - 128 MB
 Monitor - VGA
 Storage - At least 7mb
 Peripherals - Mouse, Keyboard, CD ROM

13
 SYSTEM TESTING

Testing: - According to IEEE,” testing means the process of analyzing an s/w item
to detect the difference between existing and required condition and to evaluate the
feature of the s/w item”.

White Box Testing: - In this testing technique the internal structure of s/w
component in tested. White box testing is also known as glass box testing. It is test
case, design method that uses the control structure of the procedural design test
cases.

Black Box Testing: - In black box testing, the structure of the program is not
considered. Text case is decided on the basis of requirement or specification of the
program or modeling and the internals of the modules or the program are not
considered for selection of cases.

14
DATA FLOW DIAGRAM (DFD)

15
Data Flow Diagram:-

The project dictionary contains an entry for each DFD developed during
analysis. Thus there is a context diagram. A top level DFD and detailed diagrams
for all top level functions and their components. Each DFD has a unique number
and can be reference by that number.
DFD is a graphics representation of system that shows data flow to, frame
and within the system, processing functions that change data in some manner and
the storage this data.
DFD are nothing but more than network of a related system functions
(processing of data) that indicate from where information (data) is received
(inputs) and to where it is send (outputs). It is also called as bubble charges.
DFD’s are more detailed than content diagram. DFD’s are used to despite
specifics data flows (movement of inform) from both the physical view point (How
it is dine) and the logical view point (what is done).
DFD use a number of symbols to represent system. Most data flow
modeling methods use four kinds of symbols these symbols are used to represent
four kinds of system components.
1-processes
2-data stores
3-data flows
4-external entities

16
 0 LEVEL DFD:-

PURCHASE INFORMATION SALE INFROMATION

PROVISION STORE
MANAGEMENT

STOCK INFORMATION REPORT ACCESS

CUSTOMER INFORMATION

17
1 LEVEL DATA FLOW DIAGRAM:-

PROVISION STORE MANAGEMENT

USER NAME PASSWORD

LOGIN

PROVISION STORE
MANAGEMENT

MDI FORM

CUSTOMER INFO SALE FORM PURCHASE FORM STOCK FORM

DATABASE DATABASE

DATABASE DATABASE

18
 ENTITY RELATIONSHIP DIAGRAM (E-R DIAGRAM
CUSTOMER
NAME ADDRESS
BILL NO. BILL NO. DATE
DATE

S.NO

SALE EMPLOYEE STOCK

TOTAL S.NO
QTY AMOUNT QTY

RATE PARTICULER
PARTICULER
AMOUNT PRODUCT

ADDRESS
DATE
DELEAR NAME

S.NO CUSTOMER NAME INVOICE NO. MOBILE NO.

CUSTOMER INFO EMPLOYEE PURCHASE

S.NO.
TOTAL
MOBILE NO.
AMOUNT
ADDRESS
PARTICULER

QTY AMOUNT
RATE

19
DATABASE DESIGN

20
SALE TABLE

21
PURCHASE TABLE

22
STOCK TABLE

23
CUSTOMER INFORMATION TABLE

24
INPUT/OUTPUT SCREEN
25
LOGIN FORM

26
SPLASH FORM

MDI FORM
27
28
SALES FORM

29
PURCHASE FORM

30
STOCK FORM

31
CUSTOMER INFO FORM

32
CODING

LOGIN FORM

33
Private Sub Command1_Click()
If Text1.Text = "ishwar" And Text2.Text = "2019" Then
Unload Me
Form2.Show
Else
MsgBox "Invalid password try again!"
Text1.Text = " "
Text2.Text = " "
Text1.SetFocus
End If
End Sub

Private Sub Command2_Click()

Unload Me
End Sub

SPLASH FORM

Private Sub Timer1_Timer()

On Error Resume Next
p1.Value = p1.Value + 10
If p1.Value = 100 Then
Unload Me
MDIForm1.Show
End If
End Sub

34
 MDI FORM

Private Sub Toolbar1_ButtonClick(ByVal Button As MSComctlLib.Button)

Select Case Button.Key
Case "sa"
form3.Show
Case "pr"
Form4.Show
Case "st"
Form5.Show
Case "cu"
Form6.Show
Case "re"
Unload Me
End Select
End Sub

Private Sub Toolbar1_ButtonMenuClick(ByVal ButtonMenu As

MSComctlLib.ButtonMenu)
Select Case ButtonMenu.Key
Case "sa"
DataReport1.Show
Case "pr"
DataReport2.Show
Case "st"
DataReport3.Show
Case "cu"
DataReport4.Show
Unload Me
End Select
End Sub

35
 SALE FORM

Dim cm As New Connection

Dim rs As New Recordset
Dim rs1 As New Recordset

Private Sub Command1_Click()

Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
Text7.Text = " "
Text8.Text = " "
Text9.Text = " "
Text10.Text = " "
End Sub

Private Sub Command10_Click()

rs.MovePrevious
If rs.BOF Then
rs.MoveLast
End If
showdata
End Sub

Private Sub Command2_Click()

rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(9) = Text10.Text
End Sub

36
Private Sub Command3_Click()
rs!billno = Text1.Text
rs!customername = Text2.Text
rs!address = Text3.Text
rs!Date = Text4.Text
rs!sno = Text5.Text
rs!particuler = Text6.Text
rs!qty = Text7.Text
rs!Rate = Text8.Text
rs!amount = Text9.Text
rs!totalamount = Text10.Text
End Sub

Private Sub Command4_Click()

Dim m As Integer
m = MsgBox("are you sure delete record", vbYesNo)
If m = vbNo Then
Exit Sub
Else
rs.Delete
rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End If
End Sub

Private Sub Command5_Click()

Dim a As Variant
a = InputBox("enter billno", Find)
rs1.Open "select * from sale where billno =" & a & "", cm, adOpenKeyset,
adLockOptimistic
If Not rs1.EOF Then
Text1.Text = rs1(0)
Text2.Text = rs1(1)
Text3.Text = rs1(2)
Text4.Text = rs1(3)
Text5.Text = rs1(4)
Text6.Text = rs1(5)
Text7.Text = rs1(6)
Text8.Text = rs1(7)
Text9.Text = rs1(8)
Text10.Text = rs1(9)
Else

37
MsgBox "record not found"
End If
End Sub

Private Sub Command6_Click()

If DataEnvironment1.rsCommand5.State Then
DataEnvironment1.rsCommand5.Close
End If
Dim ad1 As Variant
ad1 = Val(Text1.Text)
DataEnvironment1.Command5 ad1
DataReport5.Show
End Sub

Private Sub Command7_Click()

rs.MoveFirst
showdata
End Sub

Private Sub Command8_Click()

rs.MoveLast
showdata
End Sub

Private Sub Command9_Click()

rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End Sub

Private Sub Form_Load()

With cm
.Provider = "microsoft.jet.oledb.4.0"
.ConnectionString = "D:\book shop\book.mdb"
.Open
End With
rs.Open "select * from sale", cm, adOpenKeyset, adLockOptimistic
showdata
End Sub
Public Sub showdata()
Text1.Text = rs!billno

38
Text2.Text = rs!customername
Text3.Text = rs!address
Text4.Text = rs!Date
Text5.Text = rs!sno
Text6.Text = rs!particuler
Text7.Text = rs!qty
Text8.Text = rs!Rate
Text9.Text = rs!amount
Text10.Text = rs!totalamount
End Sub

PURCHASE FORM
Dim cm As New Connection
Dim rs As New Recordset
Dim rs1 As New Recordset

Private Sub Command1_Click()

Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
Text7.Text = " "
Text8.Text = " "
Text9.Text = " "
Text10.Text = " "
Text11.Text = " "
End Sub

Private Sub Command10_Click()

rs.MovePrevious
If rs.BOF Then
rs.MoveLast
End If
showdata
End Sub

Private Sub Command2_Click()

39
rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(9) = Text10.Text
rs(10) = tetx11.Text
End Sub

Private Sub Command3_Click()

rs!invoiceno = Text1.Text
rs!dealername = Text2.Text
rs!address = Text3.Text
rs!mobileno = Text4.Text
rs!Date = Text5.Text
rs!sno = Text6.Text
rs!particuler = Text7.Text
rs!qty = Text8.Text
rs!Rate = Text9.Text
rs!amount = Text10.Text
rs!totalamount = Text11.Text
End Sub

Private Sub Command4_Click()

Dim m As Integer
m = MsgBox("are you sure delete record", vbYesNo)
If m = vbNo Then
Exit Sub
Else
rs.Delete
rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End If
40
End Sub

Private Sub Command5_Click()

Dim a As Variant
a = InputBox("enter invoiceno", Find)
rs1.Open "select * from purchase where invoiceno =" & a & "", cm, adOpenKeyset,
adLockOptimistic
If Not rs1.EOF Then
Text1.Text = rs1(0)
Text2.Text = rs1(1)
Text3.Text = rs1(2)
Text4.Text = rs1(3)
Text5.Text = rs1(4)
Text6.Text = rs1(5)
Text7.Text = rs1(6)
Text8.Text = rs1(7)
Text9.Text = rs1(8)
Text10.Text = rs1(9)
Text11.Text = rs1(10)
Else
MsgBox "record not found"
End If
End Sub

Private Sub Command6_Click()

If DataEnvironment1.rsCommand6.State Then
DataEnvironment1.rsCommand6.Close
End If
Dim ad1 As Variant
ad1 = Val(Text1.Text)
DataEnvironment1.Command6 ad1
DataReport6.Show
End Sub

Private Sub Command7_Click()

rs.MoveFirst
showdata
End Sub

Private Sub Command8_Click()

rs.MoveLast
41
showdata
End Sub

Private Sub Command9_Click()

rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End Sub

Private Sub Form_Load()

With cm
.Provider = "microsoft.jet.oledb.4.0"
.ConnectionString = "D:\book shop\book.mdb"
.Open
End With
rs.Open "select * from purchase", cm, adOpenKeyset, adLockOptimistic
showdata
End Sub
Public Sub showdata()
Text1.Text = rs!invoiceno
Text2.Text = rs!dealername
Text3.Text = rs!address
Text4.Text = rs!mobileno
Text5.Text = rs!Date
Text6.Text = rs!sno
Text7.Text = rs!particuler
Text8.Text = rs!qty
Text9.Text = rs!Rate
Text10.Text = rs!amount
Text11.Text = rs!totalamount
End Sub

STOCK FORM
Dim cm As New Connection

42
Dim rs As New Recordset
Dim rs1 As New Recordset

Private Sub Command1_Click()

Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
End Sub

Private Sub Command10_Click()

rs.MovePrevious
If rs.BOF Then
rs.MoveLast
End If
showdata
End Sub

Private Sub Command2_Click()

rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
End Sub

Private Sub Command3_Click()

rs!billno = Text1.Text
rs!Date = Text2.Text
rs!sno = Text3.Text
rs!Descriptionofgoods = Text4.Text
rs!qty = Text5.Text
rs!amount = Text6.Text
End Sub

Private Sub Command4_Click()

Dim m As Integer
43
m = MsgBox("are you sure delete record", vbYesNo)
If m = vbNo Then
Exit Sub
Else
rs.Delete
rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End If
End Sub

Private Sub Command5_Click()

Dim a As Variant
a = InputBox("enter billno", Find)
rs1.Open "select * from stock where billno =" & a & "", cm, adOpenKeyset,
adLockOptimistic
If Not rs1.EOF Then
Text1.Text = rs1!billno
Text2.Text = rs1!Date
Text3.Text = rs1!sno
Text4.Text = rs1!particuler
Text5.Text = rs1!qty
Text6.Text = rs1!amount
Else
MsgBox "record not found"
End If
End Sub

Private Sub Command6_Click()

If DataEnvironment1.rsCommand7.State Then
DataEnvironment1.rsCommand7.Close
End If
Dim ad1 As Variant
ad1 = Val(Text1.Text)
DataEnvironment1.Command7 ad1
DataReport7.Show
End Sub

Private Sub Command7_Click()

44
rs.MoveFirst
showdata
End Sub

Private Sub Command8_Click()

rs.MoveLast
showdata
End Sub

Private Sub Command9_Click()

rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End Sub

Private Sub Form_Load()

With cm
.Provider = "microsoft.jet.oledb.4.0"
.ConnectionString = "D:\BOOK SHOP\book.mdb"
.Open
End With
rs.Open "select * from stock", cm, adOpenKeyset, adLockOptimistic
showdata
End Sub
Public Sub showdata()
Text1.Text = rs!billno
Text2.Text = rs!Date
Text3.Text = rs!sno
Text4.Text = rs!particuler
Text5.Text = rs!qty
Text6.Text = rs!amount
End Sub

CUSTOMER INFO FORM

Dim cm As New Connection

Dim rs As New Recordset

45
Dim rs1 As New Recordset

Private Sub Command1_Click()

Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
End Sub

Private Sub Command10_Click()

rs.MovePrevious
If rs.BOF Then
rs.MoveLast
End If
showdata
End Sub

Private Sub Command2_Click()

rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
End Sub

Private Sub Command3_Click()

rs!sno = Text1.Text
rs!customername = Text2.Text
rs!address = Text3.Text
rs!mobileno = Text4.Text
End Sub

Private Sub Command4_Click()

Dim m As Integer
m = MsgBox("are you sure delete record", vbYesNo)
If m = vbNo Then
Exit Sub
Else
rs.Delete
rs.MoveNext
If rs.EOF Then
46
rs.MoveFirst
End If
showdata
End If
End Sub

Private Sub Command5_Click()

Dim a As Variant
a = InputBox("enter sno", Find)
rs1.Open "select * from customerinfo where sno =" & a & "", cm, adOpenKeyset,
adLockOptimistic
If Not rs1.EOF Then
Text1.Text = rs1!sno
Text2.Text = rs1!customername
Text3.Text = rs1!address
Text4.Text = rs1!mobileno
Else
MsgBox "record not found"
End If
End Sub

Private Sub Command6_Click()

If DataEnvironment1.rsCommand8.State Then
DataEnvironment1.rsCommand8.Close
End If
Dim ad1 As Variant
ad1 = Val(Text1.Text)
DataEnvironment1.Command8 ad1
DataReport8.Show
End Sub

Private Sub Command7_Click()

rs.MoveFirst
showdata
End Sub

Private Sub Command8_Click()

rs.MoveLast
showdata
End Sub

47
Private Sub Command9_Click()
rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End Sub

Private Sub Form_Load()

With cm
.Provider = "microsoft.jet.oledb.4.0"
.ConnectionString = "D:\book shop\book.mdb"
.Open
End With
rs.Open "select * from customerinfo", cm, adOpenKeyset, adLockOptimistic
showdata
End Sub
Public Sub showdata()
Text1.Text = rs!sno
Text2.Text = rs!customername
Text3.Text = rs!address
Text4.Text = rs!mobileno
End Sub

48
DATA REPORT

SALE REPORT

49
50
PURCHASE REPORT

51
STOCK REPORT

52
CUSTOMER INFO REPORT

53
SALE PRINT REPORT

54
55
PURCHASE PRINT REPORT

56
STOCK PRINT REPORT

57
CUSTOMER INFO PRINT REPORT

58
 CONCLUSION

the project entitled “BOOK SHOP MANAGEMENT” is

developed in Visual Basic6.0 as Front End and Ms-Access 2003 as Back End
used as database . This project is made for book shop management System .
It controls all the transaction sale,purchase and stock of good detail etc. It
also generates the reports in specific manner.
So this project is very useful for “BOOK SHOP MANAGEMENT”. It
reduces extra work and it very reliable. In this project icon and other
components are understandable.

59
 REFERENCES

The references contains reference to all the documents that were referred for the
creation and completion of the project. It contains the Names of the referred
software engineering documents, visual basic technical and stadards.

1. VISUAL BASIC 6.0 IN RECAREL TIMETM – STEVEN

BROWN
2. MASTERING VISUAL BASIC 6.0 – EVANGELOUS
PETROUTSON
3. VISUAL BASIC 6.0 HOW TO PROGRAM – DETEL & DELEL,
T.R.NIETO
4. www.a1vbcode.com
5. Software Engineering-Roger Pressmen
6. System Analysis and Design – Elias M. Awad
60
INTERNET

61