CHAPTER-I

INTRODUCTION

1.1 ABOUT THE PROJECT

The project called “VEHICLE PARKING ALLOTMENT SYSTEM” which
maintains all information about the customers car parking alert details. The goal of this project is
to minimize the work done by staff to provide the details for a car parking area and space to the
customers.

This project involves the customer, employee, parking place, facility, car and bike
allotment, car and Bike leaving, car and Bike allot and amount collection details. It maintains
the information of customer car parking areas and leaving the cars in every day.

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. Searching and finding a particular detail of a car 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 daily car Bike parking, collection amount details and maintains the satisfaction of
the customer details.

This system facilitate easy of maintenance and to provide a quick view of all the details
according to the transactions of customers car parking and staffs maintaining. Alert process is
simple and error free. But it is impossible in the manual system.

This software is competent of producing reports regarding maintenance consists of

various stages.
The project classified main modules are as follows :

1
Master Module

 Employee Details

 Customer Details

 Car Allotment Details

 Car Leaving Details

Transaction Module
 Car Allotment Status Details
 Customer Monthly Payment Details
 Daily Amount Collection Details

Report Module
 Employee Report
 Customer Report
 Car Allotment Report
 Car Leaving Report

2
1.2 Organizational Profile

Thiru.K.Thavasiappan started “PRS VEHICLE STAND” in the year 2015. It is one of

the famous parking in Tirupur. It was established with an ultimate aim to give good service
based on the customers.

In this company more than 5 members are working. More than 5 families are being
benefited through this company. 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.

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 parking space. Searching and finding a
particular detail of a cement stock 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 system, which is followed at present, is a manual system. The type of manual entry
made so many corrections in the reporting time and frequent occurrence of error. Important
drawback of existing system is time factor. It would not be help management to precede the
problem in entry time. It will take long time to prepare reports or else.

The main objective of this project is to overcome the drawbacks of the existing system.
This can be accommodates by the use of computer with a specified programming language to
handle the operations.

The existing system is fully based on manual work each and every activity of the existing
system was performed manually. It will take a huge time for during each and every activity and
take more man power. So it is necessary to computerize the system.

2.1.1 DRAWBACKS OF THE EXISTING SYSTEM

 Manual work.
 Security of information is low.
 Available spaces are not identified.
 A lot of time consumed.
 Needs of lot of manpower.
 Frequent occurrence of error.
 Calculations are difficult.
 There is no provision for giving deduction amount for customers.

4
2.2. PROPOSED SYSTEM

The system, which is proposed, now computerizes all the details that are maintained
manually. Once the details are fed into the computer there is no need for various persons to deal
with separate sections.

Only a single person is enough to maintain all the reports. The security can also be given
as per the requirement of the users. Its also help us to give timing task then the user could give
the receipt also in printout format.

2.2.1 FEATURES OF THE PROPOSED SYSTEM

 Large volumes of data can be stored.

 Security is assured.
 Maintenance of file is flexible.
 Records are easily stored and updated.
 Reports can be generated.
 Easily know the parking cars and available spaces.
 Accurate calculations are made.
 Less manpower required.

5
2.3 FEASIBILITY STUDY

The feasibility study is carried out to test whether the proposed system in words is
being implemented . The feasibility study is based on three major factors;

ECONOMICAL FEASIBILITY

Economical feasibility is the most recently used method for evaluating effectiveness
of the proposed system . It is obliquely known as cost benefit analysis . This procedure
determined the benefits and savings that are expected from the proposed system and
compared with the cost of the existing system .

TECHNICAL FEASIBILITY

Technical analysis centers on the existing computer system ( hardware , software

etc. , ) and to what extent it can support the proposed addition . This involves financial
considerations to accommodate technical enhancement . If the budget is a serious constraint ,
than the project is judged not feasible .

BEHAVIORAL FEASIBILITY

An estimate should be made of how strong a reaction the user staff is likely to
have toward the development of computerized system . It is common knowledge the
computer installations have something to do with turnover , transfers and changes in
employee job status .

6
 CHAPTER-III
SYSTEM SPECIFICATION

3.1 SYSTEM SPECIFICATION

3.1.1 HARDWARE SPECIFICATION

MONITOR : LCD MONITOR 15” COLOR
PROCESSOR : INTEL PENTIUM
HARD DISK : 550 GB
MOUSE : OPTICAL MOUSE
KEYBOARD : 104 KEYS
RAM : 4 GB

3.1.2 SOFTWARE SPECIFICATION

OPERATING SYSTEM : MICROSOFT XP
FRONT-END : VISUAL BASIC 6.0
BACK-END : MS-ACCESS

7
3.2 AN OVERVIEW OF SOFTWARE

VISUAL BASIC 6.0

3.2.1 LANGUAGE SPECIFICATION VISUAL BASIC 6.0
Microsoft Visual Basic is the newest version of the popular programming
language. With its features, Visual Basic is even stronger contender in the application
development area then ever before . It makes uses of graphical user interface (GUI) for creating
robust and powerful application. GUI suggests use illustration to text, when enable user to
interact with an application. The feature makes it easier to comprehend things in quicker and
easier way.

Coding in GUI environment is quiet transition to traditional . Linear programming

methods when the user is guided through is linear path execution and is limited to a small set of
operation in GUI environment , the number of option to the user is much greater allowing more
freedom to user and developers .

Visual basic was developing from basic programming language. Microsoft got its
start by developing ROM based interpreted BASIC from early microprocessor base computer .
In 1982, Microsoft quick basic and legitimize as serious development language for MS - DOS
environment .

Features
> Easier comprehension
> User friendliness
> Faster application development
> to active x technology
> Develop robust stand - alone applications , games and utilities in less time than it takes in other
languages .
> Interactive screen handling facilities .

8
 Visual Basic is just one of the languages you can use to program your applications .
The language is only one aspect of a Windows application. The visual interface of the
application isn't tied to a specific language , and the same tools you'll use to develop your
application's interface will also be used by all programmers , regardless of the language they'll
use to code the application .

To simplify the process of application development , Visual Studio provides an

environment that's common to all languages , known as an integrated development
environment ( IDE ) . The purpose of the IDE is to enable the developer to do as much as
possible with visual tools before writing code . Even as you write code , the IDE will help
you in many ways . For example , it underlines errors , it suggests the keywords that may
appear at the current place in your code in a list , and it even provides tools for locating
and fixing errors ( a process known as debugging ) .

The IDE provides tools for designing , executing , and debugging your
applications . It will be a while before you explore all the elements of the IDE , and I will
explain the various items as needed in the course of the book . In the following sections ,
you'll look at the basic components of the IDE you'll be using to build simple Windows
applications . You'll learn how its tools allow you to quickly design the user interface of
your application as well as how to program the application . The IDE is your second
desktop , and you'll be spending most of your productive hours in this environment .

The Start Page When you run Visual Studio for the first time , you will be
prompted to select the type of projects you plan to build so that the environment can be
optimized for that specific type of development . I'm assuming that you have initially
selected the Visual Basic Development settings , which will optimize your copy of Visual
Studio for building Windows and web applications with Visual Basic . You can always
change these settings , as explained at the end of this section . After the initial
configuration , you will see a window , The Recent Projects tab will be empty , of course
, unless you have already created some test projects .

9
 Visual Studio will detect the settings of a previous installation , so if you're
upgrading from an earlier version of Visual Studio , the initial screen will not be identical
. On the Start Page window of Visual Studio , you will see the following panes under the
Get Started heading : Welcome Click the Welcome tab to see a series of links that
provide developer assistance for using Visual Studio . These links include What's New In
Visual Studio , Creating Applications With Visual Studio , and Extending Visual Studio ,
among others . Other related links may be added as this book goes to the printer .

Windows Here you'll find a list of topics related to Windows application

development . Windows applications , frequently referred to as desktop applications , are
the applications you install on a local computer and execute locally . Web Here you'll
find a list of topics related to web application development .

Web applications are executed on a remote computer , the web server , and
you interact with them through a browser . Cloud , Office , SharePoint In addition to
Windows and web applications , Visual Studio can be used to develop applications for
Office and SharePoint as well as applications that use a new Microsoft platform for
building distributed applications , the Azure platform . These three types of projects
aren't discussed in this book .

Data Here you'll find a list of topics related to data - driven programming .
All applications that interact with a database are data driven ; they can be Windows or
web applications . The principles of interacting with a database ( retrieve , display , and
update database data ) are the same regardless of whether you use them to build Windows
or web applications . Recent Projects Here you see a list of the projects you opened most
recently with Visual Studio , and you can select the one you want to open again chances
are you will continue working on the same project as the last time . Each project name is
a hyperlink , and you can open a project by clicking its name .

Above the list of recent projects there are two hyperlinks one for creating a new
project and another one for opening a new solution. You will find more information on
solutions and projects later in this chapter. Most developers will skip the Start Page. To
do so , open the Tools menu and choose the Import And Export Settings command to
start a configuration wizard . In the first dialog box of the wizard, select the Reset All

10
Settings check box and then click the Next button . The next screen of the wizard
prompts you for a location in which to save the new settings so that Visual Studio can
read them every time it starts . Leave the default location as is and click Next again to see
the last screen of the wizard , in which you're prompted to select a default collection of
settings .

This collection your system I installed Visual Studio 2010 with depends on the
options you've installed Visual Basic only on my system , and I was offered the following
options ( among others ) : General Development Settings , Visual Basic Development
Settings , and Web Development . For the default configuration of my copy of Visual
Studio , and for the purpose of this book , I chose Visual Basic Development Settings so
that Visual Studio could optimize the environment for a typical VB developer .

OVERVIEW OF BACK-END

3.2.2 ABOUT MS-ACCESS 2007

MS - ACCESS Access is a super powerful program with dozens of features

to help with the information management because Microsoft constantly expenses the
capacity of access for both new database users and programmers . In Ms - Access the
database means a collection of tables that hold data . It is also a relation database which
can define relationships between types of information . It supports so many data types
more users can incorporated data form other applications.

Features
> New object properties , methods and other language elements .
> Creating custom objects with the class module .
> Customizing menus and tool in the applications .
> Using data access object it access ODBC database without loading the MS jet
database engine .
> Using the object browser a reference for the objects and their members .
> Improving performance by the usage of database and tables .
> Microsoft Access provides an array of new and enhanced objects methods , properties
, functions , statements , data types , and events to create powerful database application
using with Visual Basic . It doesn't load software components that aren't required for all

11
database such as Visual Basic for application and Data Access object , until they are
needed : this shortens the time it takes a database to load and improves overall
performance .
> Many forms and reports can be opened much faster , because forms and report that do
not have event procedures any linker include a form or report module .

Before examining the table examples in this book , it's a good idea to have a
firm understanding of the terminology used when working with databases especially
Access databases . Microsoft Access follows most , but not all , traditional database
terminology . The terms database , table , record , field , and value indicate a hierarchy
from largest to smallest . These same terms are used with virtually all database systems
, so you should learn them well . Databases Generally , the word database is a computer
term for a collection of information concerning a certain topic or business application .

Databases help you organize this related information in a logical fashion for
easy access and retrieval . Some older database systems used the term database to
describe individual tables . Current use of database applies to all elements of a database
system , Databases aren't only for computers .

There are also manual databases; we sometimes refer to these as manual filing
systems or manual database systems. These filing systems usually consist of people,
papers, folders, and filing cabinets paper is the key to a manual database system . In a
real manual database system, you probably have in / out baskets and some type of
formal filing method. You access information manually by opening a file cabinet,
taking out a file folder, and finding the correct piece of paper . Users fill out paper
forms for input, perhaps by using a keyboard to input information that is printed on
forms. You find information by manually sorting the papers or by copying information
from many papers to another piece of paper (or even into an Excel spreadsheet) .

You may use a spreadsheet or calculator to analyze the data or display it in new
and interesting ways . An Access database is nothing more than an automated version of
the filing and retrieval functions of a paper filing system . Access databases store
information in a carefully defined structure . Access tables store a variety of different
kinds of data, from simple lines of text ( such as name and address ) to complex data
12
such as pictures , sounds , or video images . Storing data in a precise format enables a
database management system (DBMS) like Access to turn data into useful information .
Tables serve as the primary data repository in an Access database. Queries, forms, and
reports provide access to the data , enabling a user to add or extract data , and
presenting the data in useful ways . Most developers add macros or Visual Basic for
Applications (VBA) code to forms and reports to make their Access applications easier
to use. A relational database management system (RDBMS) , such as Access , stores
data in related tables . For example, a table containing employee data (names and
addresses) may be related to a table containing payroll information (pay date , pay
amount , and check number) . In fact, one of the fundamental differences between a
relational database and a manual filing

Access is such a rich and powerful application that most people do not know how to
use it. Access makes it easy for users to work with databases. You can create tables, edit data
and queries to find the data you want with little effort and access includes wizards that can do
the work of designing data entry forms, reports and mailing labels.

Access also makes it easy for developers to create application. It includes an entire
programming language, visual basic for applications, and its interface is so powerful that
developers can create many customs application without programming. Access requires forms,
reports and macros are powerful enough to do most of the work that used to do required
programming.

13
 CHAPTER - IV

SYSTEM DESIGN AND DEVELOPMENT

4.1 DATABASE 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 subsystem of a whole of the system can itself be considered a
system with its own complements.

The Database Management System (DBMS) consists of a collection of interrelated

data and a set of programs to access that 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 thought of as the logical
design of the base data structures used to store the data. In the relational model these are
the tables and views. 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 to 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.

14
4.2 FILE DESIGN
The file design is the last phase that indicates the final system and process of the final
system. In the design phase of „ VEHICLE PARKING ALLOTMENT SYSTEM‟, the
database tables, input screen design and output design etc. are designed.

 The database tables where 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 novice user can invoke the system.
 Reports generated here give the minute information, which helps the manager to take
vital decisions.

4.3 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 users. The system should be users
friendly to gain appropriate information to the user.

Forms for input design in this project are:

 Employee Details
 Customer Details
 Car Allotment Details
 Car Leaving Details
 Car Allotment Status Details
 Customer Monthly Payment Details
 Daily Amount Collection Details

15
4.4 OUTPUT 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 outputs are those whose destination will be outside the organization. Interactive
outputs are those, in which user uses in communicating directly with computer.

The reports given in this project are:

 Employee Report
 Customer Report
 Car Allotment Report
 Car Leaving Report

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 systems 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 organization‟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 ReReseach

17
4.5.1 DESCRIPTION OF MODULES

MASTER MODULE
This will store and maintain the details of employee, customer, Car allotment and Car
leaving details.

Employee Details
This module maintains the information about the employee details. It
contains the fields are employee id, name of the employee, gender, date of birth, qualification,
address, phone number shift and salary details.

Customer Details
This module maintains the information about the customers details. It contains the fields
are customer id, name of the customer, address, phone number, Car number, Car type, payment
type, registration amount and registration date details.

Car Parking Allotment Details

This module maintains the information about the Car allotment details. It contains the
fields are date, allotment number, customer id, customer name, Car number, Car type, payment
type, parking date and employee id details.
Car Leaving Details
This module maintains the information about the Car leaving details. It contains the
fields are date, allotment number, customer id, customer name, Car number, Car type, payment
type, leaving date, leaving time, verified, number of days and amount details.

Transaction Module
Transaction module can be used to maintain the details for the Car allotment status,
customer monthly payment and daily amount collection details.

Car Allotment Status Details

This module maintains the information about the Car allotment status details.
It contains the fields are Car number and allotment status details.

Customer Monthly Payment Details

This module maintains the information about the customers monthly payment details. It
contains the fields are customer id, name of the customer, Car number, Car type, payment type,
month and year, payment amount and payment date details

18
Daily Amount Collection Details
This module maintains the information about the customers daily amount collection
details. It contains the fields are customer id, name of the customer, Car number, Car type,
payment type and amount details.

REPORT MODULE

The reports will generate automatically. This is maintained and calculated accurately.
The reports are displayed in neat formats.

 Employee Report
 Customer Report
 Car Allotment Report
 Car Leaving Report

19
 CHAPTER – V

SYSTEM TESTING AND 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 parking place. All the reports
and the screens are tested for their validity and values in the data tables are checked for their
correctness and consistency. After successful testing of the system, it was ready for
implementation.

Various types of testing:

 Unit testing
 Integration testing
 Validation testing
 Whitebox testing
 Blackbox testing

Unit Testing
In this testing, 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.

This testing was carried out during programming stage itself. In the testing step, each
module is found to be working satisfactory as regards to the expected output from the module.

20
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 modules have its

individual programs, these program were tested individually. At last all these programs were

combined together.

The candidate system has passed the test and the system implementation is undergoing.
This was done by testing and comparing the actual output with the expected output. When there
was discrepancy, the sequence of instructions was traced to determine the problem.

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 exists.

The function or performance‟s characteristics conform to specification are expected. A

derivation 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.

Whitebox 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 methods.

 Guarantee that all independent paths within a module have been exercised
at least one.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds.

21
Blackbox 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

Implementation is the stage of the project when the theoretical design is turned into a
working system. It can be considered to be the most critical stage in achieving a successful new
system and in giving the user confidence that the new system will work and be effective.

Every developed system must be implementing to fulfill the mode of development.

There are many software implementation methods. After designing of the system is over, the
user was consulted with a demonstration. This is done to find if any logical error occur in the
system.

Therefore implementation is the process of converting a new or revised system design

into an operational one. Thus during this stage the theoretical design is turned into a working
system. If the implementation stage is not carefully planned and controlled, it can cause chaos.
Generally, there are three types of implementation as follows :

 Implementation of a computer system to replace a manual system.

 . Implementation of a new computer system to replace an existing one.
 Implementation of a modified application to replace the existing one using the same.

22
 CHAPTER -VI
CONCLUSION

CONCLUSION

The developed system is flexible and changes can be made whenever necessary speed
and changes and accuracy are enhanced computer outputs are obtained more quickly in desired
formats.

The project entitled “VEHICLE PARKING ALLOTMENT SYSTEMS” of describe

so far has designed, tested and documented completely. The package has been developed to
overcome the problems with the existing system. The software produced is so useful that the
system efficiency provides the required information at any time, regarding car parking centre.

The software created is attractive and user-friendly. It is highly interactive too. The
software appears more flexible, which is completely menu-driven, it gives advantage, as it needs
less typing by the user. It maintains data consistency. The system reduces workload and
produces adequate and timely information as and when required.

SUGGESTIONS

Any project which is done is having room for development. It can be enhanced with
various options according to the customer satisfaction in future.

It can also have an inbuilt module to completely manage the employees are attend the
customers suggestions. That is it can have a feedback module with this for develop or solving the
customer‟s requirements of the car parking facilities. All the details regarding monthly collection
amount can be added to this with valuable report generation.

23
 BIBLIOGRAPHY

I BOOK REFERENCES

1. Elias M.Awad, “System Analysis and Design ”, Galgoti y

Publications(P) Ltd, Second Edition 1996.

2. Gary Cornell , “Visual Basic 6.0 ”, Tata MC Graw -Hill Publications(P)

Ltd, Fourth Edition 1999.

3. Roger Pressman, “Software engineering ”, Tata MC Graw -Hill

Publications(P) Ltd, Fourth Edition 1994.

4. Ragu Ramakrishnan , “Database Management System ”, Tata MC Graw -

Hill Publications(P) Ltd, Third Edition 1992.

5. Naveen Prakash, “Software engineering ”, Tata MC Graw-Hill

Publications(P) Ltd, Second Edition, 1994.

II URL REFERENCES
1. http://www.vb6.us/tutorials/ms-accesss-and-visual-basic-using-ado
2. http://download.ms-access.com/docs/B10952-01/o4o00069.Access
3. http:/Visualbasicnetblogspot.com/2011/connect-ms-access-database-using-visual.

24
 APPENDICES

A) DATA FLOW DIAGRAM

ADMIN

Employee Customer Parking Facility

Details Place
Details Details
Details

employee_details customerdetails parkingplacedetails facilitydetails

Allotment
Details
allotmentdetails

Leaving leavingdetails
Details

Status
Details statusdetails

Payment
Details paymentdetails

CUSTOMER

25
B) TABLE STRUCTURE

Table Name : login_details

Purpose : This table store about the login details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

uname Text 15 Primary key User Name
password Text 30 Not Null Password

Table Name : customer_details

Purpose : This table store about the customer details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

cusid Number 10 Primary key Customer ID
cusname Text 25 Not Null Customer Name
addrs Text 30 Not Null Address
pno Number 10 Not Null Phone Number
vehno Text 10 Not Null Car Number
vehtype Text 10 Not Null Car type
paytype Text 10 Not Null Payment type
regamt Number 6 Not Null Registration amount
rdate Date/time 10 Not Null Registration Date

26
Table Name : employee_details
Purpose : This table store about the employee details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

empid Number 10 Primary key Employee ID
empname Text 20 Not Null Employee Name
gender Text 6 Not Null Gender
dob Date/time 10 Not Null Date of Birth
qualification Text 20 Not Null Qualification
addrs Text 30 Not Null Address
pno Number 12 Not Null Phone Number
shift Text 15 Not Null Shift
sal Number 8 Not Null Salary

Table Name : allotment_details

Purpose : This table store about the Car allotment details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

date Date/time 10 Not Null Date
allotno Number 20 Primary key Allotment Number
cusid Number 10 Foreign key Customer ID
cusname Text 20 Not Null Customer Name
vehno Text 10 Not Null Car Number
vehtype Text 10 Not Null Car Type
paytype Text 10 Not Null Payment Type
ptime Date/time 10 Not Null Parking Time
eid Number 6 Not Null Employee ID

27
Table Name : leaving_details
Purpose : This table store about the leaving details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

allotno Number 20 Primary key Allotment Number
aldate Date/time 10 Not Null Allotment Date
cusid Number 10 Foreign key Customer ID
cusname Text 20 Not Null Customer Name
vehno Text 10 Not Null Car Number
vehtype Text 10 Not Null Car type
paytype Text 10 Not Null Payment type
leadate Date/time 10 Not Null Leaving Date
leatime Date/time 10 Not Null Leaving time
veri Text 10 Not Null Verified
ndays Number 6 Not Null Number of days
amt Number 6 Not Null Amount

Table Name : payment_details

Purpose : This table store about the customer monthly payment details

FIELD NAME DATA TYPE SIZE CONSTRAINTS DESCRIPTION

cusid Number 10 Foreign key Customer ID
cusname Text 20 Not Null Customer Name
vehno Text 10 Not Null Car Number
vehtype Text 10 Not Null Car type
paytype Text 10 Not Null Payment type
month Text 15 Not Null Month & Year
pamt Number 6 Not Null Payment Amount
pdate Date/time 10 Not Null Payment Date

28
C) SAMPLE CODING

Dim db As New ADODB.Connection

Dim PO As New ADODB.Recordset
Dim ST As New ADODB.Recordset
Private Sub Combo1_CLICK()
ST.MoveFirst
Do While Not ST.EOF
If Trim(UCase(ST(0))) = Trim(UCase(Combo1)) Then
Text1 = ST(1)
Text2 = ST(4)
Text3 = ST(5)
Text4 = ST(6)
Exit Do
End If
ST.MoveNext
Loop
Exit Sub
ST.MoveNext
End Sub
'Private Sub Combo2_CLICK()
Private Sub Combo2_LostFocus()
If (Text4.Text = "2 WHEELER") Then
Text5.Text = 200
Else
Text5.Text = 500
End If
End Sub
Private Sub Command1_Click() 'new
Call CLEAR
Combo1.SetFocus
End Sub
Private Sub Command10_Click() 'mnext
PO.MoveNext

29
Call view
End Sub
Private Sub Command11_Click() 'mpre
PO.MovePrevious
Call view
End Sub
Private Sub Command12_Click() 'mlast
PO.MoveLast
Call view
End Sub
Private Sub Command13_Click()
MDIForm1.Show
End Sub
Private Sub Command2_Click() 'save
Call SAVE
Call CLEAR
Combo1.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")
r = InputBox("ENTER THE ID:")
If Trim(r) = "" Then
MsgBox ("PLEASE GIVE ID")
Exit Sub
End If
PO.MoveFirst
While Not PO.EOF
If UCase(Trim(r)) = UCase(Trim(PO(0))) Then
30
Call DISPLAY
Exit Sub
End If
PO.MoveNext
Wend
MsgBox ("PLEASE VERIFY THE ID")
End Sub
Private Sub Command6_Click() 'update
PO(0) = Combo1.Text
PO(1) = Text1.Text
PO(2) = Text2.Text
PO(3) = Text3.Text
PO(4) = Text4.Text
PO(5) = Combo2.Text
PO(6) = Text5.Text
PO(7) = DTPicker1
PO.Update
MsgBox "Updated"
Call CLEAR
If PO.BOF Then
Text1.Text = 1
Else
PO.MoveLast
Text1.Text = VAL(PO(0)) + 1
End If
End Sub
Private Sub Command7_Click() 'DEL
MsgBox ("ARE YOU WANT TO DELETE")
r = InputBox("ENTER THE ID:")
If Trim(r) = "" Then
MsgBox ("PLEASE GIVE ID")
Exit Sub
End If
PO.MoveFirst
31
While Not PO.EOF
If UCase(Trim(r)) = UCase(Trim(PO(0))) Then
Call DISPLAY
PO.Delete
MsgBox ("RECORD DELETED")
Call CLEAR
Exit Sub
End If
PO.MoveNext
Wend
MsgBox ("PLEASE VERIFY")
If PO.BOF Then
Combo1.Text = 1
Else
PO.MoveLast
Combo1.Text = VAL(PO(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 ID")
Exit Sub
End If
PO.MoveFirst
While Not PO.EOF
If UCase(Trim(r)) = UCase(Trim(PO(0))) Then
Call DISPLAY
Exit Sub
End If
PO.MoveNext
Wend
MsgBox ("PLEASE VERIFY THE ID")
32
End Sub
Private Sub Command9_Click() 'mfirst
PO.MoveFirst
Call view
End Sub
Private Sub Form_Activate()
End Sub
Private Sub Form_Load()
db.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\CAR.mdb;Persist
Security Info=False"
PO.Open "select * from PAYMENT", db, adOpenDynamic, adLockPessimistic
ST.Open "select * from CUSTOMER", db, adOpenDynamic, adLockPessimistic
Me.WindowState = 2
'Combo1.AddItem "2 WHEELER"
'Combo1.AddItem "4 WHEELER"
'Combo2.AddItem "DAILY"
'Combo2.AddItem "MONTHLY"
Combo2.AddItem "JUNE 2014"
Combo2.AddItem "JULY 2014"
Combo2.AddItem "AUGUST 2014"
Combo2.AddItem "SEPTEMBER 2014"
Combo2.AddItem "OCTOBER 2014"
Combo2.AddItem "NOVEMBER 2014"
Combo2.AddItem "DECEMBER 2014"
ST.MoveFirst
If Not ST.EOF Then
Do While Not ST.EOF
Combo1.AddItem (ST(0))
ST.MoveNext
Loop
End If
End Sub
Public Sub CLEAR()
Text1.Text = ""
33
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Combo1.Text = ""
Combo2.Text = ""
End Sub
Public Sub SAVE()
PO.AddNew
PO(0) = Combo1.Text
PO(1) = Text1.Text
PO(2) = Text2.Text
PO(3) = Text3.Text
PO(4) = Text4.Text
PO(5) = Combo2.Text
PO(6) = Text5.Text
PO(7) = DTPicker1
PO.Update
MsgBox "Data Stored"
End Sub
Public Sub DISPLAY() 'USE MODIFY OR SEAR, UPDATE, DEL
Combo1 = PO(0)
Text1 = PO(1)
Text2 = PO(2)
Text3 = PO(3)
Text4 = PO(4)
Combo2 = PO(5)
Text5 = PO(6)
DTPicker1 = PO(7)
End Sub
Public Sub view() 'USE ALL MOVE FIR, NEXT, PRE, LAST
If PO.BOF = True Then
PO.MoveFirst
ElseIf PO.EOF = True Then
34
PO.MoveLast
End If
Combo1 = PO(0)
Text1 = PO(1)
Text2 = PO(2)
Text3 = PO(3)
Text4 = PO(4)
Combo2 = PO(5)
Text5 = PO(6)
DTPicker1 = PO(7)
End Sub
Private Sub Form_Unload(Cancel As Integer)
db.Close
End Sub

35
D) SAMPLE INPUT

LOGIN FORM

36
MASTER MENU

37
EMPLOYEE DETAILS

38
CUSTOMER DETAILS

39
CAR ALLOTMENT DETAILS

40
CAR LEAVING DETAILS

41
TRANSACTION MENU

42
CUSTOMER MONTHLY PAYMENT DETAILS

43
CAR ALLOTMENT STATUS DETAILS

44
DATEWISE AMOUNT COLLECTION DETAILS

45
E) SAMPLE OUTPUT

REPORT MENU

46
EMPLOYEE REPORT

47
CUSTOMER REPORT

48
CAR ALLOTMENT REPORT

49
CAR LEAVING REPORT

50