Project Report

(2018 –2019)

HOTEL INFORMATION SYSTEM

SUBMITED FOR

MASTER OF SCIENCE IN COMPUTER SCIENCE

[MSC(CS)]

APSU, REWA(M.P.)

SUBMITED BY GUIDED BY
C

MAHATMA GANDHI COLLEGE SATNA (M.P)

 CERTIFICATE

This is to certify that REETU CHAUDHARY,RAJESH KUMAR SAKET,NEERAJ

KUMAR KUSHWAHA,NILESH KUMAR AHIRWAR has completed his Minor
Project work for during the academic year 2018-2019 in the partial fullfillment of the
award of MSC(CS) I SEMESTER.

Internal Examiner External Examiner

MAHATMA GANDHI COLLEGE SATNA (M.P)

 CERTIFICATE

This is to certify that REETU CHAUDHARY,RAJESH KUMAR SAKET,NEERAJ

KUMAR KUSHWAHA,NILESH KUMAR AHIRWAR has completed his Minor

Project work for during the academic year 2018-2019 in the partial fullfilment of the

award of MSC(CS) I SEMESTER

Project Guide Principal

(Mr.RAVI PANDEY) (Mr. B.L TIWARI)

MAHATMA GANDHI COLLEGE SATNA (M.P)

 Self Certificate

I hereby declared that the all project works entitled

HOTEL INFORMATION SYSTEM

Has been successfully completed by Us

In partial fulfillment for the

MASTER OF SCIENCE IN COMPUTER SCIENCE
[MSC(CS)]

Awarded By
APSU,REWA(M.P.)

During the academic session 2018-2019 under guidance of

Mr.RAVI PANDEY
This project has not been submitted for the award of any
examination.
Candidate
REETU CHAUDHARY
RAJESH KUMARSAKET
NEERAJ KUMAR KUSHWAHA
NILESH KUMAR AHIRWAR
 ACKNOWLEDGEMENT
We wish to acknowledgement with deep gratitude the valuable assistance
received by us form our guide Mr.RAVI PANDEYWho guided and encouraged us
throughout the development of this project. We would like to very many thanks Mr.
SATENDRA GAUTAMfor his valuable suggestion. It is due to encouragement
provided by him that projects could its final stage.

We also acknowledge out to Mr. NITIN SHUKLA (Director) other lecturer’s

friends. Who us in the satisfactory completion of this project.

Finally we specially thanks our parents and the near dear once who are the
another of our lives for their support and understanding.

REETU CHAUDHARY
RAJESH KUMARSAKET
NEERAJ KUMAR KUSHWAHA
NILESH KUMAR AHIRWAR
 DECLARATION

We hereby affirm that the project report titled “HOTEL INFORMATION SYSTEM
submitted by us to MAHATMA GANDHI COLLEGEaffiliated by A.P.S,U. REWA (M.P.),

for consideration of MASTER OF COMPUTER SCIENCE(MSC(CS)) embodies our work, except the

and suggestions received during the work which has been duly acknowledged.

REETU CHAUDHARY
RAJESH KUMARSAKET
NEERAJ KUMAR KUSHWAHA
NILESH KUMAR AHIRWAR
 CONTENTS

1. Preface

2. Package used :

………..Visual Basic.Net 2003

………..MS Access 2000

3. Introduction

4. Objective of Project

5. Problem Study

6. H/W & S/W requirements

7. About The System Development Life Cycle

8. Flow Chart of the project

9. Structure of database

10. Layout

11. How to use the system

12. Source Code

13. Limitation
 14. Conclusion

15. Bibliography

PREFACE

A database is a control repository information of i.e. database is

physical grouping of a collection of individual but in a predictable and

structured way it cuts redundancy data access.

RELATIONAL DATABASE

A relational database is one in which data is around in the form of a

matrix with the row of the matrix forming each individual record in the

database and columns of the matrix formatting the individual fields of

information across all records.

Database Management System (D.B.M.S.)

A database management system is an integrated software system

that has facilities for defining the physical structure of the data in a

database and for accessing entering and deleting data.

The item data within the database are primary liked in unit usually

refine data as records. The process of pacifying the values of some data
item retrieves data and capsizing the system to retrieve he values of some

or all of the data item of a records or records attaching the specification.

 PACKAGE USED
Visual Studio 2003 (.NET ) :-

Microsoft’s .NET initiative is broad-based and very ambitious. It includes the .NET
Framework,which encompasses the language and execution plateform, plus
extensive classs libraries providing rich built-in functionality. Besides the
core .NET Framework, the .NET initiative includs protocols to provide anew level
of software integration over the internet, via a standard known as web services

Although Web services are important, the foundation of all .NET-based

system is the Framework. This chapter will look at the .NET Framework
from the viewpoint of a Visual Basic developer. Unless you are quite familiar
with the Framework already, you should consider this itroduction an
essential first step in assimilating the information about Visual Basic .NET
that will be presenting in the rest of this book.

The first released product based on the .NET Framework was Visual
Studio .NET, which was publicaly launched in February of 2002, and included
version 1.0 of the .NET Framework. The current version is Visual Studio .NET
2003, but almost all of the examples will work transparently with VS.NET
2002 because the different in the two versions are minor.

Why use Visual Basic .Net:-

Visual Basic 6 was easily the most popular language for developing
application with the DNA model. as noted above, it can be used in two major
roles-forms-based VB clients and COM components.

despite its popularity, VB6 suffered from a number of limitations in the

COM/DNA environment. Some of the most serious limitations include:

No capability for multithreading

Lack of implementation inheritence and other object-oriented feachers
Poor error handling ability
Poor integration with other languages such as C++
No effictive user interface for Internet-based application

VB6’s limited object-Oriented feathers, in particular the lack of inheritence,

made it unsuitable for developement of object-based frameworks, and
denied design option to VB6 developers that were avilable to C++ or java
developer.
 About the Database window

The Database window in Microsoft Access 2000 provides a variety of

options for viewing and manipulating database objects.

 Use the Database window toolbar Quickly find commands for

creating, opening, or managing database objects.

 Use the Objects bar View database objects in the Objects bar — its
vertical orientation makes it easier to use.

 Organize database objects into groups Click the Groups bar to

view your groups, which can contain shortcuts to database objects of
different types.

 Use new object shortcuts In the Database window, quickly create

a new database object by using a wizard, or open a new database
object in design view.

 Customize how you select and open objects in the Database

window If you choose, change the default behavior so that you
select a database object by resting the pointer over it, and open an
object by single-clicking it.

 Select an object by typing its name For example, select the

Shippers table while viewing the list of table objects by typing .
What's new about working with data and database design?

Microsoft Access 2000 provides many new features that make

working with data and designing a database even easier.

 Use record-level locking A Microsoft Access database now

supports record-level locking, in addition to page-level locking (which
locks all records on a 4K page). You enable the locking level with the
new database option, Open databases using record level
locking (Tools menu, Options command, Advanced Tab). The
actual level that is used depends on how the Access database is
programmed.

 Find and replace You can now move freely between the Find and
Replace dialog boxes and the data in the view or window.

 View related data in a sub datasheet Use a sub datasheet to

view and edit related or joined data in a table, query, or form
datasheet, or in a sub form all from the same view. For example, in the
North wind sample database the Suppliers table has a one-to-many
relationship with the Products table; so for each row of the Suppliers
table in Datasheet view, you can view and edit the related rows of the
Products table in a sub datasheet.

 Automatically fix errors caused by renaming fields Name

AutoCorrect automatically corrects common side effects that occur
 when you rename forms, reports, tables, queries, fields, text boxes or
other controls.

 Take advantage of Unicode support Use the characters of any

language that Unicode supports in your data. Use Unicode
compression to offset the effect of Unicode's increased storage space
requirements. Take advantage of dual-font support — specify a
substitute font that you can use in addition to your default font to
properly display all of the characters in your data.

 Use Microsoft ActiveX Data Objects (ADO) Use Microsoft

ActiveX Data Objects (ADO) to access and manipulate data in a
database server through any OLE DB provider.
 Introduction

Now a day in the field of computition we have required

accrate and sufficient information at very fast. In mannual
system it is not possible analso very lengthly work. If we are
using manual then we have to face inaccuracy,insufficieny
and more invaluable time is being consumed.
We have designed a super market information system
project in which we have provided the facility of
purchasing,salling ,modifying,deleting products and adding a
customer also.
Report facility is available in every event.so now I
understand that this project will full fill the need of
marketing of any product.
This application software is titled ‘HOTEL
INFORMATION SYSTEM” Application software is user
friendly which is made in visual basic.net.
Computer have help automatic of many industrial and
business system.they are used extensively in
manufacturing and
processing.industries,power_distribution system banking
system and other finance_company. Computer aided
design and computer aided memory are becoming very
popular among large industrial and an eshtablishment
 OBJECTIVE OF PROJECT

Computer become versatile enough perform job of various nature computer is able
to store volume data. Manipulate it and provide accurate and efficient information. Now
a range of computer is available with different capability and specialty, which are made
to suit different users.

Whenever a new project is taken or new application program is developed it has

certain objective may very form system. The main objective of our software is to
provide the information to student. The main objective of the software follows: -

1. Provide better service.

2. To make working efficient, fast and effective.
3. To easily query details.
4. To get error free work.
 Problem Study

In existing system, Computerise Home Loan data related to various

entities and activities manually.

Problem in existing system:

1. Time consuming: As the system is not computerized and a lot

of work are done manually it consumes a significant amount of time.
It is required to prepare the result as early as possible ,which not
possible in the existing system.

2.Accuracy: Accuracy is statistically necessarily for result

preparation, which is not possible in the existing system. There
may be changes of making mistakes while considering such a complex
problem manually.

3.Detailed report: The existing system is unable to give the

detailed report due to non-availability of information in database.

4.Paper work: As the existing system is manual, lots of paper work

has to be done.

5.Sequrity: There is a lack of security and privacy checks in existing

system. Any body can be access and modify the information in to
registers.

6.Static: The existing system is not dynamic and can’t accept the
changes at advanced stage .
 HARDWARE REQUIREMENT

Type of CPU PC-IV

MEMORY (RAM) 500 MB (MINIMUM)

Disk HARD DISK 40 GB minimum

VDU MONO OR COLOUR MONITOR

KEYBOARD ANY OF THE CURRENTLY BEING

USED KEYBOARD

PRINTER ANY PRINTER (L&T, WINPRO,

PANASONIC)

SOFTWARE REQUIREMENT

This project has been developed with the help of fourth generation

language on Visual Basic .NET 2003

OPERATING SYSTEM : Windows XP SP2

SOFTWARE USED : Visual Basic .NET 2003

SYSTEM DEVELOPMENT LIFE CYCLE

System development life cycle include following phases:-

…..Recognition of Needs
.....Feasibility Study
…..Analysis
…..System Design
…..Development
…..System Testing
…..Implementation
…..Maintenance
 RECOGNITION OF NEEDS

The terms “System Analysis” and “System design” are often

encountered; “System Investigation” includes these as well as
other activities. A system investigation is a project undertaken to
improve a specific aspect of the information system; its essence is
working with people to devise systems that help people work
better. A systems investigation some times called “Systems
development project”, relies on an extensive body of methodology
and a well define set of tools and techniques in order to analyze,
design, and implement an information system or a portion of an
information system.
 FEASIBILTY STUDY
A feasibility study is undertaken to determine the possibility of either
improving the existing system or developing a totally new system. The
feasibility study is a test of a system proposal according to its workability,
impact of the organization of the preliminary investigation is the
determination that the system required is feasible.

Economic Feasibility:
A system that can be developed technically and that will be
used if installed must be a good investment for the organization.
Economic analysis is the most frequently used method for evaluating
the effectiveness of the system. More commonly known as
cost/benefit analysis, the procedure is to determine the benefit and
saving that are expected from the system and compare them with
cost.

As far as the economic feasibility is concerned, this project is

economic feasible. Because neither it requires a costly hardware support
nor it requires a costly software support.

Technical Feasibility:
This means that the work for the project should be done with current
equipment existing software technology and available personnel. New
system Vs today’s environment and state of art purchase of equipment Vs
capital budgets. Thus management as a tool to evaluate the practicability
of developing a new system uses feasibility study.
 ANALYSIS

The analysis procedures which have been used in our project are:-

(1) Requirement analysis

(2) System analysis

(1)Requirement Analysis:

Requirement analysis involves studying the current system to find

out how it works and where improvement should be made. System
studies results in an evolution of how current method is working and
whether adjustment is necessary or possible. A requirement is feature
that must be including in a system. It may be include a way of capturing
or processing data, producing information control business activity, or
supporting management.

(2)System Analysis:

System analysis is the process of gathering and interpreting

facts diagnosing problems and using the information to recommend
improvement to the system. System analysis for business is the process of
studying a business situation to see how it operates and whether
improvement of needed tasks, carried out by system analyst. One of the
main functions of the system analyst is to convert an existing manual
system to computerized system. The system analyst does so by defining in
board outline how the problem in the outside world is to be related to a
computer system.
 SYSTEM DESIGN

During this phase the system to be developed is designed.

Design Goals:-
The system design lies at the heart of the system development
cycle. System design specific exactly how the objective set during the
system analysis phase laid the foundation of the development of the end
product.

Before developing the new system it is important to establish the

design goals, these are the standards that the developers follow during
the entire process of development so that the end product fulfills the
requirements of the user.
The developed software product must be able to fulfill the required
functional and performance test performed in the testing stage such as
exercise of code with minimal input values, execution time, response time
etc. in all combinations. The system must fulfill the criteria specified in the
functional requirements and performance requirements. Output of system
should meet the required standards of reliability, efficiency and
correctness.
If the new system meets these specifications, then the
application are fit to be distributed for installation else it must be probed
again and redesigned in such a manner that it lends itself to any
modification that might be needed in due course of use.
The software must satisfy the de facto of good software, some
of which are

User Friendly
The software should be user friendly so that user can easily
understand the controls without any particular guidance by the developers
of the application. The FAS system was designed keeping this requirement
in mind and the final User Interface was quite user friendly and all
complexity will be hidden from the user.

Integrity
 The results of the system were very crucial as they represented
the data, which would affect quite a lot no of people and financial part
needs accuracy. So special emphasis was given to the accuracy and
consistency of the system.

Modularity
As the system was quite large so the system was
designed in such a way so that the entire software was
divided into several modules, which made the system
more maintainable and easy to develop.

PROCESS AND STAGE OF SYSTEM DESIGN

The design phase focuses on the detail implementation of

the System recommended in the feasibility study. Emphasis is
on translating from a user-oriented document to a document
oriented to the Programmers or database personal .

LOGICAL & PHYSICAL DESIGN

System design goes through two phases of development .

Logical and physical design . A data flow diagram
shows the logical flow of the system and defines the boundaries
of the
system for a candidate system , it describes input
(source) .
 FROM DESIGN

The data in the forms carry information that comes from the

people and the informational output of the system goes to the

people , the physical carriers of the data of information . It can

constitute authority for action . It provides information for making

decision and improving operations .

REQUIRE OF FORM DESIGN

1. Identification and working .

2. Physical factors .
3. Order of data items .
4. Ease of data items .
5. Size of arrangement.
6. Use of instruction.
7. Efficiency consideration.

FILE ORGANISATION & DATABASE DESIGN

After designing the input and output , the designer begins to

concentrate on file design or how data should be
organized around the requirements . How data are
organized depends on the data and response requirement that
determine hardware and configurations . File organization may
be sequential, indexed , inverted list of random . An
integrated approach to the file design is the database . The
general theme is to handle the information as an integrated
whole with minimum redundancy and improve performance .
 INPUT/OUTPUT & FORM DESIGN

INPUT DESIGN

Inaccurate input data are the most common cause of

error in data processing . Error entered by the data entry
operation can be control by the input design .Input design is the
processing of converting user-oriented inputs to computer base
format .

OUTPUT DESIGN

Computer outputs are most important and

direct sources of information to user . Efficient , intelligible output
design improves the system relation with the user help in
decision-making. A major from output is a hard copy from the
printer. Printout should be design around the output requirement of
the user .

The design covers the following :-

1. Reviews the current physical system-its data flows, file

content , volumes , frequencies .

2. Prepare out specification-That is determine the format, content and

frequency of report including terminal specification and location .

3. Prepare input specification-Format , content and most of the

input function . This includes determining the flow of document
from the input stores to the actual input locations.

4. Preparing edit and security & control specification-This

specifying the rules for edit , correction , back procedure and
the controls that ensure processing and file integrity .

5. Specifies the implementation plan .

6. Prepare a logical design , walkthrough of implementation
flow , out input controls and implementation plan .

7. Reviews benefits , cost , target dates and system constraints.

SECURITY OF THE SYSTEM

PHYSICAL SECURITY :

The breakdown in electronic computers can be

in circuits or chips ,capacitors , transistors etc . Failures
in these components occur due to power supply
problems aging. Performance of a computer system is
influenced by excessive temperature , high humidity ,
dust build-up , noise Interference & magnetic fields .

Therefore we recommend the management

to follow some tips as :

1.There should be appropriate electrical environment.

2. There should be controlled temperature.

3. Have a power line conditioner feeding the computer

system .

OPERATING SYSTEM LEVEL SECURITY:

Windows 98 is the current operating

system on the user side .Oracle as a backend also
ensures operating system security so that when some
more recent version of windows or on increase of
transaction if the user shifts to even Unix also the
backend need not to be changed .
 DATABASE SECURITY:

Client has been given the facility of backup and

restoring of database so that at the end of each day
after taking the various day to day reports a backup
is taken and during any loss of data can be restored
by the client itself .

APPLICATION SECURITY:

The current GUI (Graphical User Interface)

application developed is Visual Basic 6 enables the user
to work as friendly as in windows environment.
Application security is taken care by installing all the
respective dynamic link libraries into windows system
folder ,which is again hidden from end user .These all
are taken care internally by visual studio tool of package
and development tool.

The security measures that are being given to the Client

are listed below:

1.Valid User (Unauthorized access): The person who

knows in and out of the system will only be authorized to
make data entry.

2.Proper atmosphere: An environment completely

isolated from other departments is given .A separate
IT infrastructure is developed on the client side.

TRANSACTION SECURITY:

Unless the user is a valid user or the data is valid no

transaction will be updated in the database.
Also all the RDBMS rules have been followed while
updating a transaction.
 SOFTWARE ENGINEERING PARADIGM
For creating our project we use “Linear sequential
paradigm” also called Waterfall model or Classic life cycle
model. This model suggests a systematic sequential
approach to software development that begins at the
system level and progress through analysis, design, coding,
testing and support. For developing our project we use all
these approaches sequentially.

System/Information Engineering: System engineering

and analysis contains requirement gathering at the system
level such as h/w configuration and the h/w requirement for
the s/w development. In this stage we establish
requirements for the s/w.

Software Requirement Analysis: In this process we

understand the nature of the programs to be built, the
required functions, behavior, performances interfaces.

Design: After requirement analysis we focus on the four

distinct attributes such as data structure, s/w architecture,
Interface representation, and procedural detail.

Code Generation: When we complete our design we

translate design into a machine-readable form.

Testing: Finally, when we complete our coding then we

start testing. Using several techniques and check with all
desired Input for project.
 TESTING & DEBUGGING

“ Testing is the process of finding errors from a program,

rather then extracting them.”

Most error are the result of incorrect control functions in

programs rather then incorrect computation or data manipulation .
Errors due to incorrect data manipulation are usually easiest to delete and
correct. The formers often go undetected and remain in programs after
they have been approved to run in production environment. Control
functions are those which regulate the sequence in which tasks are
performed, the number of times a loop is executed, etc.
Program testing is a continuous procedure. Testing can be done in
following steps ;

ERROR FAULT & RELIABILITY:

Once the algorithm has been expressed in pseudo-code, it is

subjected to desk check . This is a process which should be applied to
each procedure within a program and involves selecting sample value of
test data for input to the procedure and processing them precisely as
directed by the program coding to determine whether or not they will
produce a correct result .
We have checked this S/W using both “simulate” and “live” data .
Each algorithm now produces exactly the O/P , what we want ?

FUNCTIONAL TESTING :

After checking the algorithm’s validity or correctness, the

next stage of testing occurs when the coding has been freed
from syntax errors . Functional testing is referred to check the
functions of procedures procedure-by-procedure .
We check each procedure/module for its functionality and reliability .
Many logical error were found in different modules, then they are
corrected for their proper function .
Some programs may require to perform calculations on the
basic of data or input given by the user . This calculation has
been tested to give accurate results to the user .

STRUCTURAL TESTING :

Structural testing means testing of programs in structure.

This testing refers to the testing of cohesion and coupling of
different program modules. It also checks whether a program
modules produces correct output when it receives data from
another module.

For best result degree of cohesion must be high and

degree of coupling must below. In this S/W there are a number
of programs with voluminous modules. We check each programs
with different set of test data and corrected mistakes as desired
.
 IMPLEMENTATION

Introduction is the process of the having systems personnel check out

the and put new equipment into use, trained users, installed the new
application and construct any files of data needed to use it. This phase is
less creative than system design. Depending on the size of the organization
that will be involved in using the application and risk involved in its use,
system developers may chose to test the operation in only one area of the
firm with only one or two person.

There are three types of implementation:

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 an

existing one, using the same computer.

In my perspective implementation is the process of converting a new

system design into an operational one. Conversion is one aspect of
implementation, the other aspects are post implementation review and
software maintenance.
 DOCUMENTATION

Documentation is a process that will be used for developing and

maintaining documentation for installing and maintaining products
developed in the system life cycle. Documentation typically includes
training material, user document, user manual, and operations manual and
relies document. The documentation will be reviewed and approved by
concerned user of the documentation.

The purpose of documentation process is to develop and maintain the

documentation that will be used to install and operate the product. This
process also ensures that the documentation developed is synchronized
with latest product releases.

Our product document typically consist of the following:

Deliverables (file name, size etc): It includes the codes.

Test summary report.
 MAINTENANCE

The maintenance of existing software can account over 30 percent of

all effort expended by a development organization, and the percentage
continues to rise of more software is produced.

Uninitiated readers may ask why so much maintenance is required

and why so much effort is expended. Much of the software we depend on
today is on average 10 to 15 years old. Even when these programs ware
created using the best design and coding techniques known at the time and
most were not, they were created when program size and storage space
were principle concerns. They were then migrated to new platforms,
adjusted for changes in machine and operating system technology and
enhanced to meet new user needs all without enough regard to overall
architecture.

The ubiquitous nature of change underlines all software work. Change

is inevitable when computer-based system are built.

Software maintenance is, of course, for more then “fixing mistakes.” We

may defined maintenance by describing four activities that are undertaken
after a program is released for use. There are four different maintenance
activities: collective maintenance, adoptive maintenance, perfectly
maintenance or enhancement maintenance, and preventive
maintenance or reengineering. Only about 20 percent of all
maintenance work is spent “fixed mistake”. The remaining 80 percent is
spent adapting existing systems to changes in their external environment,
making enhance required by users, and reengineering an application for
future use.
 HOW TO USE THE SYSTEM

1. About us:

This module provides facility to more information about

“HOTEL INFORMATION SYSTEM”.
THE BEGINNING
Welcome to the world of “HOTEL INFORMATION System”.
2. Login :

This module provide facilities to registration of

user.
In this module provide facility to login of user ,this
module ask the user name and password of the
user , unauthorized user can not login and access
this softwere .

3. Application Form:

In the Application Form fowlling types of menu:-

EMPLOYEE info:-In this menu to use add,delete,
modify and display the information of employee.
ROOM INFORMATION:-In this menu to use add,
delete,modify and display the record of room info.
BILL INFO:-In this menu Used to maintain the news
paper stock means purchase and selling BILL
INFORMATON.
Report:-This menu used by user to show the Report of
Employee and Room and BILL report.
Accessories:-This menu have collect the extra feature
of my Project.just like as Notepad and calculator.
Windows:- This menu manages our windows in
Cascade order, Horizentol order, Verticaly order and
Arrange Icons .
Help:-This menu will be used to show the information
of about the project.
 LIMITATION

The limitation of our project are :-

(1) We have tried to develop our system as best as possible , but it is developed

on account of knowledge based collected from the responsible authorities

of the Hotel information system, information may lead to the limitation of

our project .

(2) We can’t provide any help facility in this project due to time limitation .

(3) We can use this project on stand alone system

Further scope :-

Project development , has certain limitation project has certain limitations has project
has some scope we can use in modification of this software . we will try to improve our
project in future and reduce the above problem
 Conclusion
The most important part of our project super market
information system report and provide report facility.

Genrating hotal Information Systemrecord of all transaction.

Are also important part of the system. Computer proves to be the
best thing that can perform the above mentiond task efficiently.

Thus we have tried to make our system as user friendly and

eddecient as possible using the application package Visual
Basic.Net.
 BIBLIOGRAPHY

 VB.NET Programming Black Book

By: Steven Holzner – Dreamtech Publications

 Mastering VB.NET
By: Evangelos Petroutsos – BPB Publication

 Introduction To .NET Framework

By: Worx Publication

 Msdn.microsoft.com/net/
MDI FORM:-

Public Class form1

Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub

'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer
 'NOTE: The following procedure is required by the Windows Form Designer
'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
Friend WithEvents MainMenu1 As System.Windows.Forms.MainMenu
Friend WithEvents MenuItem1 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem2 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem3 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem4 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem5 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem6 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem7 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem8 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem9 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem10 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem11 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem12 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem15 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem16 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem17 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem13 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem14 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem18 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem19 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem20 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem21 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem22 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem23 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem24 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem25 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem26 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem27 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem28 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem29 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem30 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem31 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem32 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem33 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem34 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem35 As System.Windows.Forms.MenuItem
Friend WithEvents MenuItem36 As System.Windows.Forms.MenuItem
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
Dim resources As System.Resources.ResourceManager = New
System.Resources.ResourceManager(GetType(form1))
Me.MainMenu1 = New System.Windows.Forms.MainMenu
Me.MenuItem1 = New System.Windows.Forms.MenuItem
Me.MenuItem2 = New System.Windows.Forms.MenuItem
Me.MenuItem3 = New System.Windows.Forms.MenuItem
Me.MenuItem6 = New System.Windows.Forms.MenuItem
Me.MenuItem7 = New System.Windows.Forms.MenuItem
Me.MenuItem8 = New System.Windows.Forms.MenuItem
Me.MenuItem9 = New System.Windows.Forms.MenuItem
Me.MenuItem4 = New System.Windows.Forms.MenuItem
Me.MenuItem5 = New System.Windows.Forms.MenuItem
Me.MenuItem10 = New System.Windows.Forms.MenuItem
Me.MenuItem11 = New System.Windows.Forms.MenuItem
Me.MenuItem15 = New System.Windows.Forms.MenuItem
Me.MenuItem16 = New System.Windows.Forms.MenuItem
Me.MenuItem17 = New System.Windows.Forms.MenuItem
Me.MenuItem12 = New System.Windows.Forms.MenuItem
Me.MenuItem13 = New System.Windows.Forms.MenuItem
 Me.MenuItem14 = New System.Windows.Forms.MenuItem
Me.MenuItem18 = New System.Windows.Forms.MenuItem
Me.MenuItem19 = New System.Windows.Forms.MenuItem
Me.MenuItem20 = New System.Windows.Forms.MenuItem
Me.MenuItem21 = New System.Windows.Forms.MenuItem
Me.MenuItem22 = New System.Windows.Forms.MenuItem
Me.MenuItem23 = New System.Windows.Forms.MenuItem
Me.MenuItem24 = New System.Windows.Forms.MenuItem
Me.MenuItem25 = New System.Windows.Forms.MenuItem
Me.MenuItem26 = New System.Windows.Forms.MenuItem
Me.MenuItem27 = New System.Windows.Forms.MenuItem
Me.MenuItem28 = New System.Windows.Forms.MenuItem
Me.MenuItem29 = New System.Windows.Forms.MenuItem
Me.MenuItem30 = New System.Windows.Forms.MenuItem
Me.MenuItem31 = New System.Windows.Forms.MenuItem
Me.MenuItem32 = New System.Windows.Forms.MenuItem
Me.MenuItem33 = New System.Windows.Forms.MenuItem
Me.MenuItem34 = New System.Windows.Forms.MenuItem
Me.MenuItem35 = New System.Windows.Forms.MenuItem
Me.MenuItem36 = New System.Windows.Forms.MenuItem
'
'MainMenu1
'
Me.MainMenu1.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem1, Me.MenuItem10, Me.MenuItem18, Me.MenuItem21, Me.MenuItem23,
Me.MenuItem27, Me.MenuItem32})
'
'MenuItem1
'
Me.MenuItem1.Index = 0
Me.MenuItem1.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem2, Me.MenuItem3, Me.MenuItem4, Me.MenuItem5})
Me.MenuItem1.Text = "staff"
'
'MenuItem2
'
Me.MenuItem2.Index = 0
Me.MenuItem2.Text = "new Appointmengt"
'
'MenuItem3
'
Me.MenuItem3.Index = 1
Me.MenuItem3.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem6, Me.MenuItem7, Me.MenuItem8, Me.MenuItem9})
Me.MenuItem3.Text = "Modify"
'
'MenuItem6
'
Me.MenuItem6.Index = 0
Me.MenuItem6.Text = "Employee"
'
'MenuItem7
'
Me.MenuItem7.Index = 1
Me.MenuItem7.Text = "Manager"
'
'MenuItem8
'
Me.MenuItem8.Index = 2
Me.MenuItem8.Text = "Cooks"
'
 'MenuItem9
'
Me.MenuItem9.Index = 3
Me.MenuItem9.Text = "Waiter"
'
'MenuItem4
'
Me.MenuItem4.Index = 2
Me.MenuItem4.Text = "Desplay"
'
'MenuItem5
'
Me.MenuItem5.Index = 3
Me.MenuItem5.Text = "Exit"
'
'MenuItem10
'
Me.MenuItem10.Index = 1
Me.MenuItem10.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem11, Me.MenuItem12})
Me.MenuItem10.Text = "Rooms"
'
'MenuItem11
'
Me.MenuItem11.Index = 0
Me.MenuItem11.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem15, Me.MenuItem16, Me.MenuItem17})
Me.MenuItem11.Text = "Booking"
'
'MenuItem15
'
Me.MenuItem15.Index = 0
Me.MenuItem15.Text = "Add costomer"
'
'MenuItem16
'
Me.MenuItem16.Index = 1
Me.MenuItem16.Text = "checke out"
'
'MenuItem17
'
Me.MenuItem17.Index = 2
Me.MenuItem17.Text = "display"
'
'MenuItem12
'
Me.MenuItem12.Index = 1
Me.MenuItem12.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem13, Me.MenuItem14})
Me.MenuItem12.Text = "Allotment"
'
'MenuItem13
'
Me.MenuItem13.Index = 0
Me.MenuItem13.Text = "Add room"
'
'MenuItem14
'
Me.MenuItem14.Index = 1
Me.MenuItem14.Text = "Display"
'
 'MenuItem18
'
Me.MenuItem18.Index = 2
Me.MenuItem18.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem19, Me.MenuItem20})
Me.MenuItem18.Text = "Restaurent"
'
'MenuItem19
'
Me.MenuItem19.Index = 0
Me.MenuItem19.Text = "Item menu"
'
'MenuItem20
'
Me.MenuItem20.Index = 1
Me.MenuItem20.Text = "Add service"
'
'MenuItem21
'
Me.MenuItem21.Index = 3
Me.MenuItem21.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem22})
Me.MenuItem21.Text = "Bill"
'
'MenuItem22
'
Me.MenuItem22.Index = 0
Me.MenuItem22.Text = "Restaurent Bill"
'
'MenuItem23
'
Me.MenuItem23.Index = 4
Me.MenuItem23.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem24, Me.MenuItem25, Me.MenuItem26})
Me.MenuItem23.Text = "Report"
'
'MenuItem24
'
Me.MenuItem24.Index = 0
Me.MenuItem24.Text = "Staff"
'
'MenuItem25
'
Me.MenuItem25.Index = 1
Me.MenuItem25.Text = "Rooms"
'
'MenuItem26
'
Me.MenuItem26.Index = 2
Me.MenuItem26.Text = "Bill"
'
'MenuItem27
'
Me.MenuItem27.Index = 5
Me.MenuItem27.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem28, Me.MenuItem29, Me.MenuItem30, Me.MenuItem31})
Me.MenuItem27.Text = "Window"
'
'MenuItem28
'
Me.MenuItem28.Index = 0
 Me.MenuItem28.Text = "Horizontal"
'
'MenuItem29
'
Me.MenuItem29.Index = 1
Me.MenuItem29.Text = "vertical"
'
'MenuItem30
'
Me.MenuItem30.Index = 2
Me.MenuItem30.Text = "Cascade"
'
'MenuItem31
'
Me.MenuItem31.Index = 3
Me.MenuItem31.Text = "Arrange Icon"
'
'MenuItem32
'
Me.MenuItem32.Index = 6
Me.MenuItem32.MenuItems.AddRange(New System.Windows.Forms.MenuItem()
{Me.MenuItem33, Me.MenuItem34, Me.MenuItem35, Me.MenuItem36})
Me.MenuItem32.Text = "utility"
'
'MenuItem33
'
Me.MenuItem33.Index = 0
Me.MenuItem33.Text = "Notepad"
'
'MenuItem34
'
Me.MenuItem34.Index = 1
Me.MenuItem34.Text = "calculator"
'
'MenuItem35
'
Me.MenuItem35.Index = 2
Me.MenuItem35.Text = "Ms-word"
'
'MenuItem36
'
Me.MenuItem36.Index = 3
Me.MenuItem36.Text = "Powerpoint"
'
'form1
'
Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
Me.BackgroundImage = CType(resources.GetObject("$this.BackgroundImage"),
System.Drawing.Image)
Me.ClientSize = New System.Drawing.Size(392, 266)
Me.ForeColor = System.Drawing.Color.Red
Me.IsMdiContainer = True
Me.Menu = Me.MainMenu1
Me.Name = "form1"
Me.Text = "Form1"
Me.WindowState = System.Windows.Forms.FormWindowState.Maximized

End Sub

#End Region
 Private Sub MenuItem2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MenuItem2.Click
Dim a As New Form3
a.MdiParent = Me
a.Show()

End Sub

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

System.EventArgs) Handles MenuItem7.Click
Dim a1 As New Form5
a1.MdiParent = Me
a1.Show()

End Sub

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

System.EventArgs) Handles MenuItem8.Click
Dim a1 As New Form5
a1.MdiParent = Me
a1.Show()

End Sub

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

System.EventArgs) Handles MenuItem6.Click
Dim a4 As New Form14
a4.MdiParent = Me
a4.Show()

End Sub

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

System.EventArgs) Handles MenuItem9.Click
Dim a5 As New Form7
a5.MdiParent = Me
a5.Show()

End Sub

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

System.EventArgs) Handles MenuItem15.Click
Dim a6 As New Form8
a6.MdiParent = Me
a6.Show()

End Sub

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

System.EventArgs) Handles MenuItem16.Click
Dim a7 As New Form9
a7.MdiParent = Me
a7.Show()

End Sub

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

System.EventArgs) Handles MenuItem17.Click
Dim a8 As New Form15
 a8.MdiParent = Me
a8.Show()

End Sub

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

System.EventArgs) Handles MenuItem22.Click
Dim a9 As New Form12
a9.MdiParent = Me
a9.Show()

End Sub

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

System.EventArgs) Handles MyBase.Load

End Sub
End Class

Add Room:=
Public Class Form10
Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)
If disposing Then
If Not (components Is Nothing) Then
components.Dispose()
End If
End If
MyBase.Dispose(disposing)
End Sub

'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer

'NOTE: The following procedure is required by the Windows Form Designer

'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.

'
'GroupBox2
'
Me.GroupBox2.Controls.Add(Me.Button3)
Me.GroupBox2.Controls.Add(Me.Button2)
Me.GroupBox2.Controls.Add(Me.Button1)
Me.GroupBox2.Location = New System.Drawing.Point(360, 56)
Me.GroupBox2.Name = "GroupBox2"
Me.GroupBox2.Size = New System.Drawing.Size(104, 248)
Me.GroupBox2.TabIndex = 9
Me.GroupBox2.TabStop = False
Me.GroupBox2.Text = "GroupBox2"
'
'Button3
'
Me.Button3.Location = New System.Drawing.Point(8, 184)
Me.Button3.Name = "Button3"
Me.Button3.Size = New System.Drawing.Size(88, 32)
Me.Button3.TabIndex = 2
Me.Button3.Text = "Cancle"
'
'Button2
'
Me.Button2.Location = New System.Drawing.Point(8, 112)
Me.Button2.Name = "Button2"
Me.Button2.Size = New System.Drawing.Size(88, 32)
Me.Button2.TabIndex = 1
Me.Button2.Text = "Save"
'
'Button1
'
Me.Button1.Location = New System.Drawing.Point(8, 40)
Me.Button1.Name = "Button1"
Me.Button1.Size = New System.Drawing.Size(88, 32)
Me.Button1.TabIndex = 0
Me.Button1.Text = "Add"
'
'TextBox1
'
Me.TextBox1.Location = New System.Drawing.Point(192, 56)
Me.TextBox1.Name = "TextBox1"
Me.TextBox1.Size = New System.Drawing.Size(88, 20)
Me.TextBox1.TabIndex = 10
Me.TextBox1.Text = "TextBox1"
'
'Label2
'
Me.Label2.Location = New System.Drawing.Point(56, 56)
Me.Label2.Name = "Label2"
Me.Label2.TabIndex = 12
Me.Label2.Text = "Room_no"
'
'Label3
'
Me.Label3.Location = New System.Drawing.Point(56, 88)
Me.Label3.Name = "Label3"
Me.Label3.TabIndex = 13
Me.Label3.Text = "Room_type"
'
'Label4
'
Me.Label4.Location = New System.Drawing.Point(56, 120)
Me.Label4.Name = "Label4"
Me.Label4.TabIndex = 14
Me.Label4.Text = "Room_ rent"
'
'Label5
'
Me.Label5.Location = New System.Drawing.Point(56, 152)
Me.Label5.Name = "Label5"
Me.Label5.TabIndex = 15
Me.Label5.Text = "status"
'
'Label6
'
Me.Label6.Location = New System.Drawing.Point(56, 184)
Me.Label6.Name = "Label6"
Me.Label6.TabIndex = 16
Me.Label6.Text = "manuf_name"
'
'Label7
'
Me.Label7.Location = New System.Drawing.Point(56, 216)
Me.Label7.Name = "Label7"
Me.Label7.TabIndex = 17
Me.Label7.Text = "manuf_contactno"
'
'TextBox3
'
Me.TextBox3.Location = New System.Drawing.Point(192, 112)
Me.TextBox3.Name = "TextBox3"
Me.TextBox3.Size = New System.Drawing.Size(96, 20)
Me.TextBox3.TabIndex = 18
Me.TextBox3.Text = "TextBox3"
'
'TextBox4
'
Me.TextBox4.Location = New System.Drawing.Point(192, 144)
Me.TextBox4.Name = "TextBox4"
Me.TextBox4.Size = New System.Drawing.Size(96, 20)
Me.TextBox4.TabIndex = 19
Me.TextBox4.Text = "TextBox4"
'
'TextBox5
'
Me.TextBox5.Location = New System.Drawing.Point(192, 192)
Me.TextBox5.Name = "TextBox5"
Me.TextBox5.Size = New System.Drawing.Size(96, 20)
Me.TextBox5.TabIndex = 20
Me.TextBox5.Text = "TextBox5"
'
'TextBox6
'
Me.TextBox6.Location = New System.Drawing.Point(192, 224)
Me.TextBox6.Name = "TextBox6"
Me.TextBox6.Size = New System.Drawing.Size(96, 20)
Me.TextBox6.TabIndex = 21
Me.TextBox6.Text = "TextBox6"
'
'OleDbSelectCommand1

Me.DataSet111.DataSetName = "DataSet11"
Me.DataSet111.Locale = New System.Globalization.CultureInfo("en-US")
'
'Form10
 '
Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
Me.BackgroundImage = CType(resources.GetObject("$this.BackgroundImage"),
System.Drawing.Image)
Me.ClientSize = New System.Drawing.Size(488, 350)
Me.Controls.Add(Me.TextBox6)
Me.Controls.Add(Me.TextBox5)
Me.Controls.Add(Me.TextBox4)
Me.Controls.Add(Me.TextBox3)
Me.Controls.Add(Me.Label7)
Me.Controls.Add(Me.Label6)
Me.Controls.Add(Me.Label5)
Me.Controls.Add(Me.Label4)
Me.Controls.Add(Me.Label3)
Me.Controls.Add(Me.Label2)
Me.Controls.Add(Me.TextBox1)
Me.Controls.Add(Me.GroupBox2)
Me.Controls.Add(Me.Label1)
Me.Name = "Form10"
Me.Text = "Add_room"
Me.WindowState = System.Windows.Forms.FormWindowState.Maximized
Me.GroupBox2.ResumeLayout(False)
CType(Me.DataSet111, System.ComponentModel.ISupportInitialize).EndInit()
Me.ResumeLayout(False)

End Sub

#End Region

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

System.EventArgs) Handles Button1.Click
Me.BindingContext(Me.DataSet111, "ADD_ROOM").AddNew()
End Sub

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

System.EventArgs) Handles Button2.Click
Dim ta As Object
ta = MsgBox("Are you sure to save this", MsgBoxStyle.YesNo, "update & save
information")
If ta = vbYes Then
Me.updatedataset()
Else
Me.BindingContext(Me.DataSet111, "ADD_ROOM").CancelCurrentEdit()

End If
End Sub
Sub updatedataset()
Dim db As New DataSet11

Me.BindingContext(Me.DataSet111, "ADD_ROOM").EndCurrentEdit()
db = CType(Me.DataSet111.GetChanges, DataSet11)
Me.updatedatasource(db)
Me.DataSet111.Merge(db)
Me.DataSet111.AcceptChanges()

End Sub
Sub updatedatasource(ByVal db As DataSet11)
Me.OleDbConnection1.Open()
Me.OleDbDataAdapter1.Update(db)
 Me.OleDbConnection1.Close()

End Sub

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

System.EventArgs) Handles MyBase.Load
Me.OleDbDataAdapter1.Fill(Me.DataSet111, "ADD_ROOM")
End Sub
End Class

Public Class Form11

Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

Table:-Add Customer
Table:-Add Room:-
Table:-BILL
Table:-Modify Cook
Table:-Modify Manager
Table:-Modify Waiter
New
Old user
user