venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Nithy project]

1

CHAPTER I

1. INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

Industrial Manpower Resource Organizer VB.Net projects main objective is

to maintain hierarchy of the workers inside a company. This application can help human

resource management and mangers to organize employees for allocating work and

analyzing where resource is required and where resources are wasted.

In order to maintain any single organization it should contain different managers where

each manager will handle different tasks like recruiting employees, salary management,

project management …etc. These are common for any company so industrial man power

resource organizer project will look after all these work done by managers using a simple

application.

In present scenario every industries and software companies are using this application for

effectively handling man power and reduce expenditure on project. This application is

implemented in VB.Net as front end application and SQL server as back end.

Module Description

A) Employee Creation

In the Hierarchical Organization Information System each employee is created

with their corresponding department, designation and section details.

B) Employee hierarchy

In this system Administration department is the Root Department under which

different departments exist. So the Employment hierarchy will start with root

department head like chairman and subsequently the department employees with

dept head and section employees with their section employees and for sub

departments in the departments can be identified.

2

C) Department entry/department hierarchy

In this module, Master Data for the departments can be created

employees refer this data .Sub departments Can be identified .Some of The

departments will have Different Sections

Each Department having Department heads, so department employees should

reported to the department head he might be subordinate to his superior

Department he shall report to him. Some of departments having sections so

section employees shall be reported to the section incharge he shall report to the

department head.From this Departments, sub departments the Department

hierarchy shall be created.

D) Live status

Live status gives accurate information about which Employee

Will work in which section his superior employees or his subordinates can be

identified along with their corresponding departments so that the employee info

can be managed easily.

Their performance can be monitored and if need they can be deputed to other

department as and when required this can be effectively managed.

E) Employee list enumeration

The employee details already in the database so the details can be retrieved as and

when required by taking the selective criteria from the HR manager.

F) Process details

This following process will be done to get the desired results.

Employee hierarchy can be created using Employers and their superior’s

information.

Department Hierarchy can be created using the departmental

interdependencies.

Vacancy list in various departments can be identified and prioritized by

calculating the position weight ages.

3

Employees can be transferred from one department to another based on

different criteria provided by the HR manager.

Employee retention can be processed depending their performance.

G) Job Rotation

Job rotation process will be invoked when the employee experiences monotony in

his work / duty. These will result in poor performance, some times leads to major

errors in the field of operation. This can be overcome by job rotation process. In

this the employee will be moved to other department of interest, so that the

employee will work with renovated vigor and vitality.

In some cases, to fill up the emergency vacancies, job rotation process will be

executed to avoid unforeseen delays. In any case along with the candidate /

employee his credentials and other associates will be passed to the destination

department.

H) Position Weightage

Position weightage will be calculated based on Departments weightage, section

weightage and even the designation weightage. Each position in the organization

will have certain importance in the functionality of the overall organization. The

weightage of the each position will be calculated by using the actual position in

the organization and as well as the position in the authority flow.

I) vacancies details and process details

Vacancies arised in various departments can maintained by filling the new

employees or by shifting/additional charges to existing employees.

4

1.2 ORGANIZATION PROFILE

The company was started on 21st March 2008 by M.S. & Co., Pollachi with an

objective of providing quality tractor. At present more than 50 members are working.

This company is situated just 2 kilometers from the Pollachi town, on the Pollachi-Kerala

main road. It is located in a serene pollution-free atmosphere in an area of 1 acre.

We began manufacturing tractors in the early 1960s for the Indian market. Nearly

50 years later, we are the world’s largest tractor company by volumes, with annual sales

above 214,000 tractors annually. With a presence in more than 40 countries and a

network of over 1000 dealers, Mahindra has sold well over 1.75 million tractors

worldwide. Mahindra Samriddhi is a strategic initiative of our company that envisages

rural prosperity through enhanced farm productivity. At Samriddhi centres, productivity

enhancement is ensured by providing soil and water testing facilities to farmers and

through dissemination of Innovative Farming Technologies that are sourced from various

Agricultural institutions, based in India and abroad.

Dealer Address:

M.S. & Co.,

Mahindra Tractors

Meenkarai Road,

Pollachi

5

CHAPTER II

2. SYSTEM ANALYSIS

It is important to evaluate the system’s components in relationship to one another, to

determine how requirements fit into the system. So the system analysis is concerned with

getting user requirements, analyzing it, designing and implementing it. After the

requirements collection, the information have subjected to ambiguity, omissions and

requirement consistency. Is the requirement collected from the concern are consistent

with overall objective of the system, i.e. outline of inputs from and inputs to the system

matched with proposed one.

Feasibility analysis

Existing system

Drawbacks of existing system

Proposed system

Advantages of proposed system

2.1 EXISTING SYSTEM

In existing system, all records are maintained manually.

The operation performance is very low and process is slow.

It takes a lot of time ant it’s very hard to access.

The Existing system takes more time to view the particular details by searching.

By doing manually each and every record cannot listed properly.

Searching of the information is a very tedious process.

There is no much security for data stored in register.

6

Drawback of Existing System

The time of taken for entering the details is more.

That maintains the document in separate record is very difficult to handle and the

storage space is more.

Invalid entries can be made.

Manual power is consumed.

It is very difficult to revise the whole system in case the document or data are

lost.

Maintaining several registers storing bulk of data into them is a complex process.

Several persons cannot share data in one register at a time.

2.2 PROPOSED SYSTEM

Every Organization has many managers, who are responsible for all the activities

in the organization. These managers manage different aspects of the organizational

management issues, such as manufacturing, production, Marketing, etc; one such

essential management issue is IMPRO.

As years progressed, the approach of the management changed towards the human

capital. Now Hierarchical Organization is part of every organization, and has its own

identity and importance. In this scenario, the bigger organizations need to put lot of effort

in the management of human Resources, as they are underlying capital asset to the

organization. In doing so, along with times, the Organization Information changed from

its basic operations to more strategic approach.

Advantage of proposed system

Finding ground level employee performance by the topmast manager.

Maintenance of profile details of the employees, and retrievals as and when required.

Overall & detailed view of the organization hierarchy, which is very much essential

in making effective decisions.

7

Judging the potentiality of the employees.

Maintenance of the data when the organization has many branches spread over wide

geographical area.

Accessing one branch information from another branch.

Future planning issues based on the current HR information.

Employees success planning.

Vacancy situations and their priority /effect on the organizations performance.

Employee motivational & conflict resolving issues.

8

2.3 SYSTEM CONFIGURATION

2.3.1 HARDWARE SPECIFICATION

Processor : PENTIUM IV

Speed : 2.4 GHZ

RAM : 512 MB

Hard Disk Drive : 80 GB

Monitor : SAMSUNG 17’Inch Color

Keyboard : LOGITECH 108 Keyboards

Mouse : LOGITECH Scroll Mouse

2.3.2 SOFTWARE SPECIFICATION

Operating System : Windows XP (Service pack2)

Front end : VB.Net 2005

Back end : SQL Server 2000

9

3.3.3 ABOUT THE SOFTWARE

OVERVIEW ABOUT VISUAL BASIC.NET

Microsoft.NET Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET Framework

is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object

code is stored and executed locally, executed locally but Internet-distributed, or

executed remotely.

To provide a code-execution environment that minimizes software deployment

and versioning conflicts.

To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the

.NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and the

.NET Framework class library. The common language runtime is the foundation of the

.NET Framework. You can think of the runtime as an agent that manages code at

execution time, providing core services such as memory management, thread

management, and remoting, while also enforcing strict type safety and other forms of

code accuracy that ensure security and robustness. In fact, the concept of code

management is a fundamental principle of the runtime. Code that targets the runtime is

known as managed code, while code that does not target the runtime is known as

unmanaged code. The class library, the other main component of the .NET Framework, is

a comprehensive, object-oriented collection of reusable types that you can use to develop

10

applications ranging from traditional command-line or graphical user interface (GUI)

applications to applications based on the latest innovations provided by ASP.NET, such

as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common

language runtime into their processes and initiate the execution of managed code, thereby

creating a software environment that can exploit both managed and unmanaged features.

The .NET Framework not only provides several runtime hosts, but also supports the

development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment

for managed code. ASP.NET works directly with the runtime to enable Web Forms

applications and XML Web services, both of which are discussed later in this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime (in

the form of a MIME type extension). Using Internet Explorer to host the runtime enables

you to embed managed components or Windows Forms controls in HTML documents.

Hosting the runtime in this way makes managed mobile code (similar to Microsoft®

ActiveX® controls) possible, but with significant improvements that only managed code

can offer, such as semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language runtime and

the class library to your applications and to the overall system. The illustration also

shows how managed code operates within a larger architecture.

Features of the Common Language Runtime

The common language runtime manages memory, thread execution, code execution, code

safety verification, compilation, and other system services. These features are intrinsic to

the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust,

depending on a number of factors that include their origin (such as the Internet, enterprise

11

network, or local computer). This means that a managed component might or might not

be able to perform file-access operations, registry-access operations, or other sensitive

functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an

executable embedded in a Web page can play an animation on screen or sing a song, but

cannot access their personal data, file system, or network. The security features of the

runtime thus enable legitimate Internet-deployed software to be exceptionally feature

rich.

The runtime also enforces code robustness by implementing a strict type- and code-

verification infrastructure called the common type system (CTS). The CTS ensures that

all managed code is self-describing. The various Microsoft and third-party language

compilers

Generate managed code that conforms to the CTS. This means that managed code can

consume other managed types and instances, while strictly enforcing type fidelity and

type safety.

In addition, the managed environment of the runtime eliminates many common software

issues. For example, the runtime automatically handles object layout and manages

references to objects, releasing them when they are no longer being used. This automatic

memory management resolves the two most common application errors, memory leaks

and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can

write applications in their development language of choice, yet take full advantage of the

runtime, the class library, and components written in other languages by other

developers. Any compiler vendor who chooses to target the runtime can do so. Language

compilers that target the .NET Framework make the features of the .NET Framework

available to existing code written in that language, greatly easing the migration process

for existing applications.

12

While the runtime is designed for the software of the future, it also supports software of

today and yesterday. Interoperability between managed and unmanaged code enables

developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A

feature called just-in-time (JIT) compiling enables all managed code to run in the native

machine language of the system on which it is executing. Meanwhile, the memory

manager removes the possibilities of fragmented memory and increases memory locality-

of-reference to further increase performance. Finally, the runtime can be hosted by high-

performance, server-side applications, such as Microsoft® SQL Server™ and Internet

Information Services (IIS). This infrastructure enables you to use managed code to write

your business logic, while still enjoying the superior performance of the industry's best

enterprise servers that support runtime hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate

with the common language runtime. The class library is object oriented, providing types

from which your own managed code can derive functionality. This not only makes the

.NET Framework types easy to use, but also reduces the time associated with learning

new features of the .NET Framework. In addition, third-party components can integrate

seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that

you can use to develop your own collection classes. Your collection classes will blend

seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types

enable you to accomplish a range of common programming tasks, including tasks such as

string management, data collection, database connectivity, and file access. In addition to

these common tasks, the class library includes types that support a variety of specialized

13

development scenarios. For example, you can use the .NET Framework to develop the

following types of applications and services:

Console applications.

Scripted or hosted applications.

Windows GUI applications (Windows Forms).

ASP.NET applications.

XML Web services.

Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that

vastly simplify Windows GUI development. If you write an ASP.NET Web Form

application, you can use the Web Forms classes.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the

desktop, enabling a user to perform a task. Client applications include applications such

as word processors and spreadsheets, as well as custom business applications such as

data-entry tools, reporting tools, and so on. Client applications usually employ windows,

menus, buttons, and other GUI elements, and they likely access local resources such as

the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the

managed Windows Forms control) deployed over the Internet as a Web page. This

application is much like other client applications: it is executed natively, has access to

local resources, and includes graphical elements.

In the past, developers created such applications using C/C++ in conjunction with the

Microsoft Foundation Classes (MFC) or with a rapid application development (RAD)

environment such as Microsoft® Visual Basic®. The .NET Framework incorporates

14

aspects of these existing products into a single, consistent development environment that

drastically simplifies the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed to be used

for GUI development. You can easily create command windows, buttons, menus,

toolbars, and other screen elements with the flexibility necessary to accommodate

shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual attributes

associated with forms. In some cases the underlying operating system does not support

changing these attributes directly, and in these cases the .NET Framework automatically

recreates the forms. This is one of many ways in which the .NET Framework integrates

the developer interface, making coding simpler and more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's

computer. This means that binary or natively executing code can access some of the

resources on the user's system (such as GUI elements and limited file access) without

being able to access or compromise other resources. Because of code access security,

many applications that once needed to be installed on a user's system can now be safely

deployed through the Web. Your applications can implement the features of a local

application while being deployed like a Web page.

VB.NET

ACTIVE X DATA OBJECTS.NET

ADO.NET Overview

ADO.NET is an evolution of the ADO data access model that directly addresses

user requirements for developing scalable applications. It was designed specifically for

the web with scalability, statelessness, and XML in mind.

15

ADO.NET uses some ADO objects, such as the Connection and Command objects, and

also introduces new objects. Key new ADO.NET objects include the DataSet,

DataReader, and DataAdapter.

The important distinction between this evolved stage of ADO.NET and previous data

architectures is that there exists an object -- the DataSet -- that is separate and distinct

from any data stores. Because of that, the DataSet functions as a standalone entity. You

can think of the DataSet as an always disconnected recordset that knows nothing about

the source or destination of the data it contains. Inside a DataSet, much like in a database,

there are tables, columns, relationships, constraints, views, and so forth.

A DataAdapter is the object that connects to the database to fill the DataSet. Then, it

connects back to the database to update the data there, based on operations performed

while the DataSet held the data. In the past, data processing has been primarily

connection-based. Now, in an effort to make multi-tiered apps more efficient, data

processing is turning to a message-based approach that revolves around chunks of

information. At the center of this approach is the DataAdapter, which provides a bridge to

retrieve and save data between a DataSet and its source data store. It accomplishes this by

means of requests to the appropriate SQL commands made against the data store.

The XML-based DataSet object provides a consistent programming model that works

with all models of data storage: flat, relational, and hierarchical. It does this by having no

'knowledge' of the source of its data, and by representing the data that it holds as

collections and data types. No matter what the source of the data within the DataSet is, it

is manipulated through the same set of standard APIs exposed through the DataSet and its

subordinate objects.

While the DataSet has no knowledge of the source of its data, the managed provider has

detailed and specific information. The role of the managed provider is to connect, fill,

and persist the DataSet to and from data stores. The OLE DB and SQL Server .NET Data

Providers (System.Data.OleDb and System.Data.SqlClient) that are part of the .Net

Framework provide four basic objects: the Command, Connection, DataReader and

16

DataAdapter. In the remaining sections of this document, we'll walk through each part of

the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they are,

and how to program against them.

The following sections will introduce you to some objects that have evolved, and some

that are new. These objects are:

Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database.

DataReaders. For reading a forward-only stream of data records from a SQL

Server data source.

DataSets. For storing, remoting and programming against flat data, XML data

and relational data.

DataAdapters. For pushing data into a DataSet, and reconciling data against a

database.

When dealing with connections to a database, there are two different options: SQL

Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider

(System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider.

These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data

Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath).

Connections

Connections are used to 'talk to' databases, and are respresented by provider-

specific classes such as SQLConnection. Commands travel over connections and

resultsets are returned in the form of streams which can be read by a DataReader object,

or pushed into a DataSet object.

Commands

Commands contain the information that is submitted to a database, and are

represented by provider-specific classes such as SQLCommand. A command can be a

17

stored procedure call, an UPDATE statement, or a statement that returns results. You can

also use input and output parameters, and return values as part of your command syntax.

The example below shows how to issue an INSERT statement against the Northwind

database.

Data Readers

The Data Reader object is somewhat synonymous with a read-only/forward-only

cursor over data. The Data Reader API supports flat as well as hierarchical data. A Data

Reader object is returned after executing a command against a database. The format of

the returned Data Reader object is different from a records set. For example, you might

use the Data Reader to show the results of a search list in a web page.

Data Sets and Data Adapters

DataSets

The Data Set object is similar to the ADO Record set object, but more powerful,

and with one other important distinction: the Data Set is always disconnected. The

DataSet object represents a cache of data, with database-like structures such as tables,

columns, relationships, and constraints. However, though a Data Set can and does behave

much like a database, it is important to remember that Data Set objects do not interact

directly with databases, or other source data. This allows the developer to work with a

programming model that is always consistent, regardless of where the source data resides.

Data coming from a database, an XML file, from code, or user input can all be placed

into DataSet objects. Then, as changes are made to the DataSet they can be tracked and

verified before updating the source data. The GetChanges method of the DataSet object

actually creates a second DatSet that contains only the changes to the data. This DataSet

is then used by a DataAdapter (or other objects) to update the original data source.

The DataSet has many XML characteristics, including the ability to produce and

consume XML data and XML schemas. XML schemas can be used to describe schemas

interchanged via WebServices. In fact, a DataSet with a schema can actually be compiled

for type safety and statement completion.

18

Data Adapters (OLEDB/SQL)

The Data Adapter object works as a bridge between the DataSet and the source

data. Using the provider-specific SqlDataAdapter (along with its associated SqlCommand

and SqlConnection) can increase overall performance when working with a Microsoft

SQL Server databases. For other OLE DB-supported databases, you would use the

OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection

objects.

The DataAdapter object uses commands to update the data source after changes have

been made to the DataSet. Using the Fill method of the DataAdapter calls the SELECT

command; using the Update method calls the INSERT, UPDATE or DELETE command

for each changed row. You can explicitly set these commands in order to control the

statements used at runtime to resolve changes, including the use of stored procedures. For

ad-hoc scenarios, a CommandBuilder object can generate these at run-time based upon a

select statement. However, this run-time generation requires an extra round-trip to the

server in order to gather required metadata, so explicitly providing the INSERT,

UPDATE, and DELETE commands at design time will result in better run-time

performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront.

Two new objects, the DataSet and DataAdapter, are provided for these

scenarios.

3. ADO.NET can be used to get data from a stream, or to store data in a cache for

updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order

to do inserts, updates, and deletes. You don't need to first put data into a

DataSet in order to insert, update, or delete it.

19

6. Also, you can use a DataSet to bind to the data, move through the data, and

navigate data relationships

SQL SERVER

DATABASE

A database management, or DBMS, gives the user access to their data and helps

them transform the data into information. Such database management systems include

dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create,

update and extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of

people, things and events. SQL Server stores each data item in its own fields. In SQL

Server, the fields relating to a particular person, thing or event are bundled together to

form a single complete unit of data, called a record (it can also be referred to as raw or an

occurrence). Each record is made up of a number of fields. No two fields in a record can

have the same field name.

During an SQL Server Database design project, the analysis of your business

needs identifies all the fields or attributes of interest. If your business needs change over

time, you define any additional fields or change the definition of existing fields.

SQL Server Tables

SQL Server stores records relating to each other in a table. Different tables are

created for the various groups of information. Related tables are grouped together to form

a database.

Primary Key

Every table in SQL Server has a field or a combination of fields that uniquely

identifies each record in the table. The Unique identifier is called the Primary Key, or

20

simply the Key. The primary key provides the means to distinguish one record from all

other in a table. It allows the user and the database system to identify, locate and refer to

one particular record in the database.

Relational Database

Sometimes all the information of interest to a business operation can be stored in

one table. SQL Server makes it very easy to link the data in multiple tables. Matching an

employee to the department in which they work is one example. This is what makes SQL

Server a relational database management system, or RDBMS. It stores data in two or

more tables and enables you to define relationships between the table and enables you to

define relationships between the tables.

Foreign Key

When a field is one table matches the primary key of another field is referred to as

a foreign key. A foreign key is a field or a group of fields in one table whose values

match those of the primary key of another table.

Referential Integrity

Not only does SQL Server allow you to link multiple tables, it also maintains

consistency between them. Ensuring that the data among related tables is correctly

matched is referred to as maintaining referential integrity.

Data Abstraction

A major purpose of a database system is to provide users with an abstract view of

the data. This system hides certain details of how the data is stored and maintained. Data

abstraction is divided into three levels.

Physical level: This is the lowest level of abstraction at which one describes how the data

are actually stored.

21

Conceptual Level: At this level of database abstraction all the attributed and what data

are actually stored is described and entries and relationship among them.

View level: This is the highest level of abstraction at which one describes only part of

the database.

Advantages of RDBMS

Redundancy can be avoided

Inconsistency can be eliminated

Data can be Shared

Standards can be enforced

Security restrictions ca be applied

Integrity can be maintained

Conflicting requirements can be balanced

Data independence can be achieved.

Disadvantages of DBMS

A significant disadvantage of the DBMS system is cost. In addition to the cost of

purchasing of developing the software, the hardware has to be upgraded to allow for the

extensive programs and the workspace required for their execution and storage. While

centralization reduces duplication, the lack of duplication requires that the database be

adequately backed up so that in case of failure the data can be recovered.

FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS)

because it is the only Database that meets the uncompromising requirements of today’s

most demanding information systems. From complex decision support systems (DSS) to

the most rigorous online transaction processing (OLTP) application, even application that

require simultaneous DSS and OLTP access to the same critical data, SQL Server leads

the industry in both performance and capability

22

SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched

performance, continuous operation and support for every database.

SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially

designed for online transactions processing and for handling large database application.

SQL SERVER with transactions processing option offers two features which contribute

to very high level of transaction processing throughput, which are

The row level lock manager

Enterprise wide Data Sharing

The unrivaled portability and connectivity of the SQL SERVER DBMS enables

all the systems in the organization to be linked into a singular, integrated computing

resource.

Portability

SQL SERVER is fully portable to more than 80 distinct hardware and operating

systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary

platforms. This portability gives complete freedom to choose the database sever platform

that meets the system requirements.

Open Systems

SQL SERVER offers a leading implementation of industry –standard SQL. SQL

Server’s open architecture integrates SQL SERVER and non –SQL SERVER DBMS

with industries most comprehensive collection of tools, application, and third party

software products SQL Server’s Open architecture provides transparent access to data

from other relational database and even non-relational database.

23

Distributed Data Sharing

SQL Server’s networking and distributed database capabilities to access data

stored on remote server with the same ease as if the information was stored on a single

local computer. A single SQL statement can access data at multiple sites. You can store

data where system requirements such as performance, security or availability dictate.

Unmatched Performance

The most advanced architecture in the industry allows the SQL SERVER DBMS

to deliver unmatched performance.

Sophisticated Concurrency Control

Real World applications demand access to critical data. With most database

Systems application becomes “contention bound” – which performance is limited not by

the CPU power or by disk I/O, but user waiting on one another for data access . SQL

Server employs full, unrestricted row-level locking and contention free queries to

minimize and in many cases entirely eliminates contention wait times.

No I/O Bottlenecks

SQL Server’s fast commit groups commit and deferred write technologies

dramatically reduce disk I/O bottlenecks. While some database write whole data block to

disk at commit time, SQL Server commits transactions with at most sequential log file on

disk at commit time, On high throughput systems, one sequential writes typically group

commit multiple transactions. Data read by the transaction remains as shared memory so

that other transactions may access that data without reading it again from disk.

24

CHAPTER III

3. SYSTEM DESIGN

3.1 DESIGN NOTATIONS

The design phase started by reviewing the study phase activates and making

decisions about which function are to be performing by the hardware, software and

human ware. The process of the system design is elaborate and consists of five main

stages and it becomes more and more elaborate of each stage.

The supporting diagrams are provided in order to understand the working nature

of the system. These diagrams will provide visual display, therefore it easy to understand

in pictorial way rather than in a theoretical way. Here two types of supporting diagrams

were provides as follows,

Data Flow Diagram

System Flow Diagram

25

3.1.1 DATA FLOW DIAGRAM

IMPRO

HR MANAGER

Employees

Changes for Approval

Department Heads

Department Employees

Reports/Results

IMPRO

HR MANAGER

Employees

Changes for Approval

Department Heads

Department Employees

Reports/Results

26

1

HR MANAGER DEPARTMENT HEAD

LOGIN

MENU

Appraisal

Perform

ance

Appraisal

Methods

Retention

APP APPRAISAL

RAISAL

Retained Employees

DB

Return

Vacancies List of Vacancies rotation

Admin

Hierarical

company

Master

Emplo

yee

E.H S.H D,H

O.S

27

Low Level _Login

Login db

Low Level _Dept/Section/Employee

Section employee

Dept

Dept section dept employee

H.R

D.H

VERFIC

ATION

Menu

Selection Menu

DEPT EMPLOY

EE

SECTION

ADD/MODIFY/DE

LETE

COMPONENT

DataBase

Updatate

USER

28

Low _Level Vacances/Job Rotation

Vacancies

Rotation

Employee

User Position-Weightage

Dept / section Vacani

ces

Vacanies

Priorities

Rotation

user

Job

Analysis

Vacanc

ies

Fillings

Rotation

29

low_ Level Appraisal & Retention

Employee DB

User Performance Criteria

Appraisal

Initiation Performa

nce

Checking

Appraisal

Methods

Appraisal

Action

Performance

calculation Adoption

Retention

Requirements Retention

Plans

Retention

Imitation

Appraisals

User

Retention

Retention

30

1

HR MANAGER DEPARTMENT HEAD

LOGIN

MENU

Appraisal

Perform

ance

Appraisal

Methods

Retention

APP APPRAISAL

RAISAL

Retained Employees

DB

Return

Vacancies List of Vacancies rotation

Admin

Hierarical

company

Master

Emplo

yee

E.H S.H D,H

O.S

31

Low Level _Login

Login db

Low Level _Dept/Section/Employee

Section employee

Dept

Dept section dept employee

H.R

D.H

VERFIC

ATION

Menu

Selection Menu

DEPT EMPLOY

EE

SECTION

ADD/MODIFY/DE

LETE

COMPONENT

DataBase

Updatate

USER

32

Low _Level Vacances/Job Rotation

Vacancies

Rotation

Employee

User Position-Weightage

Dept / section Vacani

ces

Vacanies

Priorities

Rotation

user

Job

Analysis

Vacanc

ies

Fillings

Rotation

33

Low _ Level Appraisal & Retention

Employee DB

User Performance Criteria

Appraisal

Initiation Performa

nce

Checking

Appraisal

Methods

Appraisal

Action

Performance

calculation Adoption

Retention

Requirements Retention

Plans

Retention

Imitation

Appraisals

User

Retention

Retention

34

3.1.2 System Flow Diagram

System flow diagram represents what the system or the application is required to do. It

allows individuals to see logical elements apart from the physical components. System

flow diagram describes the internal behavior of the system in order to deal successfully

with the environment.

Main Form

Validation

Database

Employee

Report Department

Report

Employee Depart

ment Job

Rotation Section

Login page

Section

Report Job Report

Vacancies

Vacancies

Report

35

3.2 DESIGN PROCESS

3.2.1 INPUT DESIGN

The design of input focuses on controlling the amount of input required,

controlling the errors, avoiding delay, avoiding extra steps and keeping the process

simple. The input is designed in such a way so that it provides security and ease of use

with retaining the privacy. Input Design considered the following things:

What data should be given as input?

How the data should be arranged or coded?

The dialog to guide the operating personnel in providing input.

Methods for preparing input validations and steps to follow when error

occur.

OBJECTIVES OF THE INPUT DESIGN

Input Design is the process of converting a user-oriented description of the input

into a computer-based system. This design is important to avoid errors in the data input

process and show the correct direction to the management for getting correct information

from the computerized system.

It is achieved by creating user-friendly screens for the data entry to handle large

volume of data. The goal of designing input is to make data entry easier and to be free

from errors. The data entry screen is designed in such a way that all the data manipulates

can be performed. It also provides record viewing facilities.

When the data is entered it will check for its validity. Data can be entered with the

help of screens. Thus the objective of input design is to create an input layout that is easy

to follow.

36

The main inputs of the system are

Employee Creation

In the Hierarchical Organization Information System each employee is created

with their corresponding department, designation and section details.

Job Rotation

Job rotation process will be invoked when the employee experiences monotony in

his work / duty. These will result in poor performance, some times leads to major errors

in the field of operation. This can be overcome by job rotation process. In this the

employee will be moved to other department of interest, so that the employee will work

with renovated vigor and vitality.

In some cases, to fill up the emergency vacancies, job rotation process will be executed to

avoid unforeseen delays. In any case along with the candidate / employee his credentials

and other associates will be passed to the destination department.

Position Weightage

Position weightage will be calculated based on Departments weightage, section

weightage and even the designation weightage. Each position in the organization will

have certain importance in the functionality of the overall organization. The weightage of

the each position will be calculated by using the actual position in the organization and as

well as the position in the authority flow.

Department entry/department hierarchy

In this module, Master Data for the departments can be created emplyoees refer

this data .Sub departments Can be identified .Some of The departments will have

Different Sections Each Department having Department heads ,so department employees

should reported to the department head he may be subordinate to his superior Department

he shall report to him.some of departmets having sections so section employees shall be

37

reported to the section incharge he shall report to the department head From this

Departments,subdepartments the Department heirarchy shall be created.

3.2.2 OUTPUT DESIGN

A quality output is one, which meets the requirements of the end user and presents the

information clearly. In output design it is determined how the information is to be

displaced for immediate need and also the hard copy output. It is the most important and

direct source information to the user. Efficient and intelligent output design improves the

system’s relationship to help user decision-making.

Designing computer output should proceed in an organized, well thought out manner;

the right output must be developed while ensuring that each output element is designed so

that people will find the system can use easily and effectively. When analysis designs

computer output, they should:

Identify the specific output that is needed to meet the requirements.

Select methods for presenting information.

Create document, report, or other formats that contain information produced by

the system.

The main outputs of the system are

Live status

Live status gives accurate information about which Employee Will work in which

section his superior employees or his subordinates can be identified along with their

corresponding departments so that the employee info can be managed easily.

Their performance can be monitored and if need they can be deputed to other department

as and when required this can be effectively managed.

Employee list enumeration

38

The employee details already in the database so the details can be retrived as and

when required by taking the selective criteria from the HR manager.

Process details

This following process will be done to get the desired results.

Employee hierarchy can be created using Employers and their superior’s

information.

Department Hierarchy can be created using the departmental interdependencies.

Vacancy list in various departments can be identified and prioritized by calculating

the position weightages.

Employees can be transferred from one department to another based on different

criteria provided by the HR manager.

Employee retention can be processed depending their performance.

Vacancies details and process details

Vacancies arised in various departments can maintained by filling the new

employees or by shifting/additional charges to existing employees.

Employee hierarchy

In this system Administration department is the Root Department under which

different departments exist. So the Employment heirarchy will start with root department

head like chairman and subsequently the department employees with depthead and

section employees with their section employees and for sub departments in the

departments can be identified.

39

3.2.3 DATABASE DESIGN

A database is an organized mechanism that has the capability of storing

information through which a user can retrieve stored information in an effective and

efficient manner. The data is the purpose of any database and must be protected.

The database design is a two level process. In the first step, user requirements are

gathered together and a database is designed which will meet these requirements as

clearly as possible. This step is called Information Level Design and it is taken

independent of any individual DBMS.

In the second step, this Information level design is transferred into a design for the

specific DBMS that will be used to implement the system in question. This step is called

Physical Level Design, concerned with the text characteristics of the specific DBMS that

will be used. A database design runs parallel with the system design. The organization of

the data in the database is aimed to achieve the following two major objectives.

Data Integrity

Data independence

Normalization is the process of decomposing the attributes in an application,

which results in a set of tables with very simple structure. The purpose of normalization

is to make tables as simple as possible. Normalization is carried out in this system for the

following reasons.

To structure the data so that there is no repetition of data, this helps in saving.

To permit simple retrieval of data in response to query and report request.

To simplify the maintenance of the data through updates, insertions, deletions.

To reduce the need to restructure or reorganize data which new application

requirements arise?

40

RELATIONAL DATABASE MANAGEMENT SYSTEM (RDBMS)

A relational model represents the database as a collection of relations. Each

relation resembles a table of values or file of records. In formal relational model

terminology, a row is called a tuple, a column header is called an attribute and the table is

called a relation. A relational database consists of a collection of tables, each of which is

assigned a unique name. A row in a tale represents a set of related values.

RELATIONS, DOMAINS & ATTRIBUTES

A table is a relation. The rows in a table are called tuples. A tuple is an ordered set

of n elements. Columns are referred to as attributes. Relationships have been set between

every table in the database. This ensures both Referential and Entity Relationship

Integrity. A domain D is a set of atomic values. A common method of specifying a

domain is to specify a data type from which the data values forming the domain are

drawn. It is also useful to specify a name for the domain to help in interpreting its values.

Every value in a relation is atomic, that is not decomposable.

RELATIONSHIPS

Table relationships are established using Key. The two main keys of prime

importance are Primary Key & Foreign Key. Entity Integrity and Referential Integrity

Relationships can be established with these keys. Entity Integrity enforces that no

Primary Key can have null values. Referential Integrity enforces that no Primary Key can

have null values.

Referential Integrity for each distinct Foreign Key value, there must exist a

matching Primary Key value in the same domain. Other key are Super Key and

Candidate Key.

Relationships have been set between every table in the database. This ensures

both Referential and Entity Relationship Integrity.

41

NORMALIZATION

As the name implies, it denoted putting things in the normal form. The

application developer via normalization tries to achieve a sensible organization of data

into proper tables and columns and where names can be easily correlated to the data by

the user. Normalization eliminates repeating groups at data and thereby avoids data

redundancy which proves to be a great burden on the computer resources. These includes:

Normalize the data.

Choose proper names for the tables and columns.

Choose the proper name for the data.

First Normal Form

The First Normal Form states that the domain of an attribute must include only

atomic values and that the value of any attribute in a tuple must be a single value from the

domain of that attribute. In other words 1NF disallows “relations within relations” or

“relations as attribute values within tuples”. The only attribute values permitted by 1NF

are single atomic or indivisible values.

The first step is to put the data into First Normal Form. This can be donor by

moving data into separate tables where the data is of similar type in each table. Each table

is given a Primary Key or Foreign Key as per requirement of the project. In this form new

relations for each non atomic attribute or nested relation. This eliminated repeating

groups of data.

A relation is said to be in first normal form if only if it satisfies the constraints

that contain the primary key only.

Second Normal Form

42

According to Second Normal Form, For relations where primary key contains

multiple attributes, no non key attribute should be functionally dependent on a part of the

primary key.

In this they decompose and setup a new relation for each partial key with its

dependent attributes. Make sure to keep a relation with the original primary key and any

attributes that are fully functionally dependent on it. This step helps in taking out data

that is only dependant on apart of the key.

A relation is said to be in second normal form if and only if it satisfies all the

first normal form conditions for the primary key and every non-primary key attributes of

the relation is fully dependent on its primary key alone.

Third Normal Form

According to Third Normal Form, Relation should not have a non key attribute

functionally determined by another non key attribute or by a set of non key attributes.

That is, there should be no transitive dependency on the primary key.

In this they decompose and set up relation that includes the non key attributes

that functionally determines other non key attributes. This step is taken to get rid of

anything that does not depend entirely on the Primary Key.

A relation is said to be in third normal form if only if it is in second normal

form and more over the non key attributes of the relation should not be depend on other

non key attribute.

43

TABLE DESIGN

Table Name: departments

Primary Key: dept no

Sl no Field Data Type Size Description

1 Dept no number 10 Department no

2 Dept name varchar 10 Department Name

3 Dept head varchar 10 Department Head

4 location varchar 10 Location

44

Table Name: employees

Primary Key: emp id


1 Emp id varchar 10 Employee Id

2 Emp name varchar 10 Employee Name

3 Dept no number 10 Department Number

4 Designation id varchar 10 Designation Id

5 Section id varchar 10 Section Id

6 address varchar 50 Address

7 phone varchar 15 Phone No

8 fax varchar 15 Fax

9 email varchar 50 Email Id

45

Table: Sections

Primary Key: sect id


1 Sect id varchar2 10 Section Id

2 Sect name varchar2 15 Section Name

3 Section inch varchar2 10 Section Incharge

4 Dept no number 10 Department Number

Table: designation

Primary Key: design id


1 Design id varchar2 10 Designation Id

2 designation varchar2 15 designation

Table: deptinterdependency

Primary Key: deptno


1 deptno number 10 Department Number

2 updeptno number 10 Upper Department

3 dndeptno number 10 Lower Department

46

Table: deptposweightage

Primary Key: deptno


1 deptno number 10 Department Number

2 layer number 10 Designation Layer

3 weightage number 10 Weightage

Table: desc jobrotation

Primary Key: empid


1 empid varchar2 10 Employee Id

2 presentdesignation varchar2 10 Designation

3 deputedto varchar2 10 Deputed to

4 status varchar2 50 Status

5 remarks varchar2 100 Remarks

47

Table: vacancies

Primary Key: vacancy id


1 Vacancy id varchar2 10 Vacancy id

2 Dept no number 10 Department no

3 Section id varchar2 10 Section Id

4 Designation id varchar2 10 Designation Id

5 No of vacancies number

10 No Of Vacancies

6 status varchar2 15 Status

7 Vacancy date date Vacancy Date

8 priority varchar2 50 Priority

Table: vacancyfilldetails

Primary Key: vacancyid


1 vacancyid VARCHAR2 10 Vacancy Id

2 empid VARCHAR2 10 Employee Id

3 Filled date DATE Fill Date

4 Intake details VARCHAR2 50 Intake Details

48

Table: desiglayer

Primary Key: designationid


1 designationid varchar2 10 Designation Id

2 layer number 10 Layer

3 weightage number 10 Weightage

Table: designationweightage

Primary Key:


1 designationid varchar2 10 Designation Id

2 deptno varchar2 50 Department Number

3 weightage varchar2 50 Weightage

49

CHAPTER IV

4. SYSTEM TESTING AND IMPLEMENTATION

The method of designing the system to produce desired result is accomplished in

the System development. All the facilities required for developing the new system is

acquired and computer program preparation is started.

INTRODUCTION

The development phase is the phase where the system is developed according to

the proposed system. In this phase the programs are coded, programs are coded;

programs are the entered into the computer and checked for any possible errors. After the

entire program was coded using asp. The hard copies of the reports were taken and the

debugging was subsequently made.

The designed new system is tested with the sample data and final outputs are

verified with the actual manual reports. If this reports are satisfied then the system is put

to process with on-line data entry.

The method of designing the system to produce desired result is accompanished in

the system development. All the facilities required for developing the new system

acquired and computer program preparation is started. The desired new system is tested

with sample data and final outputs are verified with oriented before implementation. It is

alone to ensure that the system objectives have been achieved successfully.

50

4.1 SYSTEM TESTING

Testing represents an interesting anomaly for software engineer. It is process of

executing a program with the intent of finding error. The tests must be traceable to the

requirement specifications. A good and efficient testing method demonstrates that

software functions appear to be working according to the specification, that behavioural

and performance requirements are being met.

NEED FOR SOFTWARE TESTING

Testing is an important component in the development of a system. The main

objectives of testing are

To ensure that all the functions of the system are working properly.

To ensure that all the system accepts correct input and behave expectedly.

To locate the errors in the system and debug them.

To ensure that the system is internally consistent.

To rectify the errors.

To provide 100 percent error free system.

To provide user free entry.

To minimize the re-work.

To add additional features.

To find unnecessary process.

The system is understandable by the user and what are the changes are needed.

51

TESTING METHODOLOGIES

White-Box Testing

This is performed knowing the internal working of the system. Tests are

conducted to ensure that the internal operations perform according to the specification

and all internal components have adequately been exercised.

White-Box testing is carried out in this project. The testing is executed by giving

the valid data types and data. By conducting this test, unnecessary codes which are

malfunctioning has been removed from the project.

The internal working of the system is tested by giving the inputs to the system

successfully.

Black-box Testing

Black box testing treats the software as a black box without any understanding as

to how the internals behave. It aims to test the functionality according to the

requirements.

Knowing the specific function that a product or module has been designed to

perform; tests can be designed to demonstrate the operational validity of each function.

This type of test design is applicable to all levels of unit, integration, functional, system

and acceptance testing.

After the completion of other testing, design of the system is tested using this

testing.

52

TYPES OF TESTING

Unit Testing

Unit testing is concerned with the testing of a small module. Using the detailed

design description as a guide, important control paths are tested to uncover the errors

within the boundary of the module. The module interface is tested to ensure that the

information flows in and out of the program unit under test. The local data structure is

ensured that the variables are exercised to ensure that all statements in the module are

executed at least once.

Integration Testing

Integration testing is proceeded with bottom up approach. In bottom up

integration testing, an individual module is first tested from a test harness. Once a set of

individual module has been tested, they are combined into a collection of modules,

known as builds, which are applied by a second harness. This process can combine until

the build consists of the entire application.

The main objective of the integration testing is to take the unit tested modules and

to build a program structure that has been dictated by design. Once all modules are unit

tested they are put together for integration testing process. All the unit-tested modules are

combined and integrated. This type of testing is a must because the information can be

lost across an interface. One module can have an inadvertent, adverse effect on the other

sub functions may not produce desired results when integrated.

User Interface Testing

The software becomes a widely used tool only if it is an easily opera table tool.

Since this is a website, care was taken to make the system to be operated even by the

novices. All the users have to do is to click and buy the products. The input devices that

are used in this system are keyboard and the mouse. And the output device is only the

53

monitor. So by using only the mouse the user can buy all the products from the website.

They have to use the keyboard only to enter their details at the time of ordering the

products.

The error messages produced by this system can be understood even to the people

who know very common English.

4.2 IMPLEMENTATION

Implementation is the stage of a project when the theoretical design is turned into

a working system. If the implementation stage is not carefully planned and controlled, it

can cause chaos. The implementation stage is a system project in its own. Implementation

is the stage of the project where the theoretical design turns into a working system. Thus

it can be considered to be the most critical stage in achieving a successful new and giving

the users confidence that the new system will work and be effective and accurate. It is

less creative than system design. It is primarily concerned with user training and site

preparation.

Depending on the nature of the system, extensive user may be required.

Implementation simply means converting a new system design into operation. An

important aspect of the system analyst’s job is to make sure that the new design is

implemented to establish standards. Implementation means the process of converting a

new raised system design into an operational one. The three types of implementation are

Implementation of a new computer system to replace an existing one.

Implementation of a modified application to replace an existing one.

Implementation of a computer system to replace a manual system.

54

CHAPTER V

5. CONCLUSION AND FUTURE ENCHANCEMENT

CONCLUSION

The newly developed system is found to be working efficiently effectively and

running satisfactorily in the environment. The pagers designed and links formed so that

the users can browse the site very easily.

The newly developed system consumes less maintenance time and it is user

friendly. Any end user can familiarize in to the system easily within some minutes. The

system is designed to be highly flexible so that any future modifications and requirements

can be easily incorporated without much design complication the goal that has been

achieved by the developed system are:

The project has been appreciated by all the users in the organization.

It is easy to use, since it uses the GUI provided in the user dialog.

User friendly screens are provided.

The usage of software increases the efficiency, decreases the effort.

It has been efficiently employed as a Site management mechanism.

It has been thoroughly tested and implemented.

FUTURE ENCHANCEMENT

The future enhancement is, like all software, ongoing. The always looking for

ways to improve the functionality, add new modules to aid the user, additional reports

and other smaller details. Our best improvements have always come from you the user

always open to suggestions and ideas, just send us an email to Technical sales will look

at all ideas and suggestions very seriously.

mailto:[email protected]

55

Whats in the pipeline

Custom Data Forms.

Attendance Points Scoring System.

Custom Data Forms.

This will give the ability to create own forms that hold data that is not currently

available in quick personnel. Well lets say you need to store information about mobile

phone details that have given to employees. They could create a custom data form that

could hold the Model, Date Given, Number, Provider etc. Quick Personnel would store

this information in data store against each employee.

Attendance Points Scoring System.

This will give the ability to assign a points system to each employee. It would

highlight areas such as consecutive lateness or illness after Bank Holidays, lateness and

illness patterns between employees and a lot more. This will allow for the analysis of

employee time keeping and attendance and route out potential future problems.

56

CHAPTERVI

6. BIBLIOGRAPHY

BOOK REFERENCES:

“Murach’s beginning VB.Net”

Author : Anne Price

Publisher : BPB Publication

Edition : First Edition.

“System Analysis and Design”

Author : ELIS.AWAD

Publisher : Galgottia Publications

Edition : 11 Edition.

WEBSITE REFFERENCE:

www.Tutorialspoint.com/vb.net/

www.homeandlearn.co/uk/net/vb.net/

www.how to startprograming.com/vb.net

57

APPENDIX

SAMPLE CODING

EMPLOYEE REGISTRATION

Imports System.Data.sqlclient

Public Class FrmEmployee

Inherits System.Windows.Forms.Form

Dim selcmd As sqlCommand

Dim da As sqlDataAdapter

Dim ds As New DataSet()

Dim inscmd As New sqlCommand()

Dim delcmd As New SqlCommand()

Dim dr As SqlDataReader

Dim s As String

Dim rno As Integer

Dim cn As New connectdatabase()

Dim d As SqlDataReader

Dim deptcmd As sqlCommand

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

System.EventArgs) Handles Button1.Click

cn.ClearFields(Me)

End Sub

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

System.EventArgs) Handles MyBase.Load

c = AddressOf clw

cn.connect()

selcmd = New SqlCommand("select * from employees", conn)

da = New sqlDataAdapter()

da.SelectCommand = selcmd

da.Fill(ds)

deptcmd = New SqlCommand("select deptno from departments", conn)

Dim d As New sqlDataAdapter(deptcmd)

d.Fill(ds, "departments")

Dim i As Integer

For i = 0 To ds.Tables("departments").Rows.Count - 1

cmbDno.Items.Add(ds.Tables("departments").Rows(i)(0))

Next

rno = 0

58

Call fillfields(rno)

End Sub

Sub fillfields(ByVal rnum As Integer)

txtEno.Text = ds.Tables(0).Rows(rnum)(0)

txtEname.Text = ds.Tables(0).Rows(rnum)(1)

cmbDno.Text = ds.Tables(0).Rows(rnum)(2)

txtDesig.Text = ds.Tables(0).Rows(rnum)(3)

cmbSecid.Text = ds.Tables(0).Rows(rnum)(4)

txtAddress.Text = ds.Tables(0).Rows(rnum)(5) & ""

txtPhone.Text = ds.Tables(0).Rows(rnum)(6) & ""

txtFax.Text = ds.Tables(0).Rows(rnum)(7) & ""

txtEmail.Text = ds.Tables(0).Rows(rnum)(8) & ""

End Sub



Dim str As String

str = "insert into employees values('" & txtEno.Text & "','" & txtEname.Text & "'," &

cmbDno.Text & ",'" & txtDesig.Text & "'," & cmbSecid.Text & ",'" & txtAddress.Text &

"','" & txtPhone.Text & "','" & txtFax.Text & "','" & txtEmail.Text & "')"

' MsgBox(str)

inscmd.Connection = conn

inscmd = New SqlCommand(str, conn)

inscmd.ExecuteNonQuery()

MsgBox("Successfully Saved")

End Sub



Try

Dim r As String

r = InputBox("Enter The eMPLOYEE Number ToDelete")

'Call efill(r)

Dim s As String

s = "delete from EMPLOYEES where EMPID='" & r & "'"

delcmd.Connection = conn

delcmd = New sqlCommand(s, conn)

Dim res As Integer

res = delcmd.ExecuteNonQuery()

'MsgBox(res)

If res = 1 Then

MsgBox("Record deleted.....")

Else

MsgBox("sorry")

End If

Catch E1 As Exception

59

MsgBox(E1.Message)

End Try

End Sub



Try

If Button3.Text = "&Edit" Then

Button3.Text = "&Update"

Dim recno As String

recno = InputBox("Enter the eMPID No to Modify...")

Call efill(recno)

Else

Dim ucmd As SqlCommand

Dim ups As String

ups = "update employees set ename='" & txtEname.Text & "',DEPTNO='" &

cmbDno.Text & "',DESIGNATIONID='" & txtDesig.Text & "',SECTIONID='" &

cmbSecid.Text & "',ADDRESS='" & txtAddress.Text & "',phone='" & txtPhone.Text &

"',fax='" & txtFax.Text & "',email='" & txtEmail.Text & "' WHERE EMPID='" &

Trim(txtEno.Text) & "'"

'MsgBox(ups)

ucmd = New sqlCommand(ups, conn)

ucmd.ExecuteNonQuery()

Button3.Text = "&Edit"

MsgBox("successfull Updated")

End If


MsgBox(E1.Message)

End Try

End Sub

Sub efill(ByVal rnumber As String)

s = "select * from Employees where empid ='" & rnumber & "'"

Dim cmd As New SqlCommand(s, conn)

dr = cmd.ExecuteReader

Dim n As Byte

n = dr.Read()

If n > 0 Then

txtEno.Text = dr.Item(0)

txtEname.Text = dr.Item(1)

cmbDno.Text = dr.Item(2)

txtDesig.Text = dr.Item(3)

cmbSecid.Text = dr.Item(4)

txtAddress.Text = dr.Item(5)

txtPhone.Text = dr.Item(6)

60

txtFax.Text = dr.Item(7)

txtEmail.Text = dr.Item(8)

Else

MsgBox("NotFound")

End If

If Not dr.IsClosed Then dr.Close()

End Sub



rno = ds.Tables(0).Rows.Count - 1


End Sub



rno = 0


End Sub



If rno > 0 Then

rno -= 1


Else

MsgBox("First Record")

End If

End Sub



If rno < ds.Tables(0).Rows.Count - 1 Then

rno += 1


Else

MsgBox("Last Record")

End If

End Sub

Public Sub clw()

Me.Hide()

End Sub

End Class

61

LOGIN FORM


Public Class FrmLogin



Dim cmd As SqlCommand

Dim dr As SqlDataReader



Try

cn.connect()

' cmd = New sqlCommand("select USERNAME,PASSWORD from login", conn)

cmd = New SqlCommand()

' cmd.CommandText = "select * from login where( (username='" &

Trim(Txtuname.Text) & "'and password= '" & Trim(txtpwd.Text) & "') and acclvl in(" &

"a" & "," & "u" & " )&" & ")"

cmd.CommandText = "select * from login where username='" & Trim(Txtuname.Text)

& "' and password= '" & Trim(txtpwd.Text) & "' and acclvl='" & Trim(TXTALVL.Text)

& "'"

'cmd.CommandText = "select * from login where( (username='" & Trim(Txtuname.Text)

& " ' and password= '" & Trim(txtpwd.Text) & "') and acclvl =('A')" & ")"

cmd.Connection = conn


Dim i As Integer

i = dr.Read

If i = -1 Then

If dr.Item(3) = Trim(TXTALVL.Text) Then

Dim obj As New Form1()

obj.Show()

Me.Hide()

Exit Sub

ElseIf dr.Item(3) = Trim(TXTALVL.Text) And dr.Item(3) = Trim("U") Then

Dim obj As New Form1()

obj.Show()

obj.MainMenu1.MenuItems(0).Enabled = False



Me.Hide()

Exit Sub

Else

MsgBox("ENTER ACCLVL EITHER A OR U ONLY")

Exit Sub

62

End If

MsgBox("NOT FOUND")

Exit Sub

End If


MsgBox("ERROR:" & vbCrLf & E1.Message)

End Try

dr.Close()

End Sub



End

End Sub

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

System.Windows.Forms.PopupEventArgs) Handles ToolTip1.Popup

End Sub

End Class

VACANCY FORM


Public Class FrmVacancyMast


Dim selcmd As SqlCommand

Dim da As sqlDataAdapter

Dim ds As New DataSet()

Dim inscmd As New sqlCommand()

Dim delcmd As New sqlCommand()

Dim dr As sqlDataReader

Dim s As String

Dim rno As Integer


Dim d As sqlDataReader

Dim deptcmd As sqlCommand

Dim desigcmd As sqlCommand

Dim seccmd As sqlCommand

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

System.EventArgs) Handles MyBase.Load

63

c = AddressOf clw

cn.connect()

selcmd = New sqlCommand("select * from vacancies", conn)

da = New sqlDataAdapter()

da.SelectCommand = selcmd

da.Fill(ds)

Dim i As Integer

deptcmd = New SqlCommand("select deptno from departments", conn)

Dim da1 As New sqlDataAdapter(deptcmd)

da1.Fill(ds, "departments")

For i = 0 To ds.Tables("departments").Rows.Count - 1

cmbdeptno.Items.Add(ds.Tables("departments").Rows(i)(0))

Next

Try

desigcmd = New sqlCommand("select designid from designation", conn)

Dim da2 As New sqlDataAdapter() 'desigcmd)

da2.SelectCommand = desigcmd

da2.Fill(ds, "designation")


MsgBox(E1.Message)

End Try

For i = 0 To ds.Tables("designation").Rows.Count - 1

cmbdesig.Items.Add(ds.Tables("designation").Rows(i)(0))

Next

seccmd = New SqlCommand("select sectid from sections", conn)

Dim da3 As New SqlDataAdapter(seccmd)

da3.Fill(ds, "sections")

For i = 0 To ds.Tables("sections").Rows.Count - 1

cmbSecno.Items.Add(ds.Tables("sections").Rows(i)(0))

Next

rno = 0


End Sub

Sub fillfields(ByVal rnum As Integer)

txtvid.Text = ds.Tables(0).Rows(rnum)(0)

cmbdeptno.Text = ds.Tables(0).Rows(rnum)(1)

cmbSecno.Text = ds.Tables(0).Rows(rnum)(2)

cmbdesig.Text = ds.Tables(0).Rows(rnum)(3)

txtnov.Text = ds.Tables(0).Rows(rnum)(4)

txtsttus.Text = ds.Tables(0).Rows(rnum)(5)

txtvdate.Text = ds.Tables(0).Rows(rnum)(6)

txtpriority.Text = ds.Tables(0).Rows(rnum)(7)

End Sub



64

Try

Dim str As String

str = "insert into VACANCIES values('" & txtvid.Text & "'," & cmbdeptno.Text & ",'" &

cmbSecno.Text & "','" & cmbdesig.Text & "'," & txtnov.Text & ",'" & txtsttus.Text &

"','" & CDate(txtvdate.Text) & "','" & txtpriority.Text & "')"

'MsgBox(str)

inscmd.Connection = conn

inscmd = New SqlCommand(str, conn)

inscmd.ExecuteNonQuery()

MsgBox("Successfully Saved")


MsgBox(E1.Message)

End Try

End Sub



Dim r As String

r = InputBox("Enter The VacancyId ToDelete")

'Call efill(r)

Dim s As String

s = "delete from vacancies where VACANCYID='" & r & "'"

delcmd.Connection = conn

delcmd = New SqlCommand(s, conn)

Dim res As Integer

res = delcmd.ExecuteNonQuery()

If res = 1 Then

MsgBox("Record deleted.....")

Else

MsgBox("sorry")

End If

End Sub



Try

If Button3.Text = "&Edit" Then

Button3.Text = "&Update"

Dim recno As String

recno = InputBox("Enter the VacancyId to Modify...")

Call efill(recno)

Else

Dim ucmd As SqlCommand

Dim ups As String

65

ups = "update vacancies set DEPTNO='" & cmbdeptno.Text & "',sectionid='" &

cmbSecno.Text & "',DESIGNATIONID='" & cmbdesig.Text &

"',NOOFVACANCIES=" & txtnov.Text & ",status='" & txtsttus.Text & "',vacancydate='"

& txtvdate.Text & "',priority='" & txtpriority.Text & "' WHERE VACANCYID='" &

Trim(txtvid.Text) & "'"

'MsgBox(ups)

ucmd = New SqlCommand(ups, conn)

ucmd.ExecuteNonQuery()

Button3.Text = "&Edit"

MsgBox("Successfully Updated")

End If


MsgBox(E1.Message)

End Try

End Sub

Sub efill(ByVal rnumber As String)

s = "select * from vacancies where vacancyid ='" & rnumber & "'"

Dim cmd As New SqlCommand(s, conn)


Dim n As Byte

n = dr.Read()

If n > 0 Then

txtvid.Text = dr.Item(0)

cmbdeptno.Text = dr.Item(1)

cmbSecno.Text = dr.Item(2)

cmbdesig.Text = dr.Item(3)

txtnov.Text = dr.Item(4)

txtsttus.Text = dr.Item(5)

txtvdate.Text = dr.Item(6)

txtpriority.Text = dr.Item(7)

Else

MsgBox("NotFound")

End If

If Not dr.IsClosed Then dr.Close()

End Sub



rno = 0


End Sub



rno = ds.Tables(0).Rows.Count - 1


66

End Sub



If rno < ds.Tables(0).Rows.Count - 1 Then

rno += 1


MsgBox("Last Record")

End If

End Sub



If rno > 0 Then

rno -= 1


Else

MsgBox("First Record")

End If

End Sub



cn.ClearFields(Me)

End Sub

Public Sub clw()

Me.Hide()

End Sub

End Class

67

SAMPLE SCREEN

68

69

70

71

72

73

74

75

76

Entertainment & Humor

venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Nithy project]