venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Mobile ne wvijay]

1

ABSTRACT

This is VB.Net Projects on Mobile Software System, which provided a lot of

facility to their user.

It has developed using VB. Net as front-end and MS-Access-2003 as Back-end

tool.

The objective and scope of my Project Mobile Software System is to record the

details various activities of user. It wills simplifies the task and reduce the paper work.

During implementation, every user will be given appropriate training to suit their specific

needs. Specific support will also be provided at key points within the academic calendar.

Training will be provided on a timely basis, and you will be trained as the new is Mobile

Software System rolled out to your area of responsibility.

Now we are in the very early stages, so it is difficult to put a specific time on the

training, but we will keep people informed as plans are developed. The system is very

user friendly and it is anticipated that functions of the system will be easily accessed by

administrators, academics, students and applicants.

This project contains the following modules

Login Module

Mobile Module

Customer Module

Showroom Module

Employee Module

Job work Module

Counseling Module

Sales Module

Service Module

2

This Project consists of various Reports such as

Mobile Report

Mobile no wise Report

Customer list Report

Date wise mobile sales Report

Bill no wise mobile sales Report

Job work list Report

Bill no mobile service Report

3

CHAPTER I

1. INTRODUCTION

1.1 OVERVIEW OF THE PROJECT

The objective and scope of my Project Mobile Software System is to

record the details various activities of user. It wills simplifies the task and reduce the

paper work. During implementation, every user will be given appropriate training to suit

their specific needs. Specific support will also be provided at key points within the

academic calendar. Training will be provided on a timely basis, and you will be trained as

the new is Mobile Software System rolled out to your area of responsibility.

MODULES DESCRIPTION

Mobile Module

In this module, we maintain the details about the mobile code, mobile

type, name, engine number, cubic capacity, engine type, head light, danger light, road

tax, color, cost, max weight.

Customer Module

In this module, we maintain the details about the customer code, customer name,

address, phone, mobile number and Email id.

Showroom Module

In this module, we maintain the details about the product code, product name, and

quantity of products.

Employee Module

In this module, we maintain the details about the employee job code, employee

name, employee designation, date of joined, year of experience.

Job work Module

In this module, we maintain the details about the job code, description, change,

date, time.

Counseling Module

4

In this module, we maintain the details about the customers who are all coming in

to the showroom for enquiry about the mobile.

Sales Module

In this module, we maintain the details about bill number, date, customer code,

name, mobile code, name, cost, registration number, registration charges, road tax, extra

fittings, insurance charges, bill amount.

Service Module

In this module, we maintain the details about the service number, service date,

customer code, name, job code, job work charges, description, labour charges, labour

name, total charges, and spare charges

This Project consists of various Reports such as

Mobile Report



Date wise mobile sales Report

Bill no wise mobile sales Report


Bill no mobile service Report

5

1.2 ORGANIZATION PROFILE

On 1st March 2009, Poorvika Mobile World commenced its first showroom

operated with 6 Employees at pollachi branch. We reached success on the opening of our

first showroom by concrete planning and providing the highest levels of service,

satisfaction and options to customers. After this successful inception, our motive was to

create a strong brand in the market and trust in customer’s mind. Having strong

confidence on our service and with continuous perseverance,

OUR SERVICES

Poorvika Mobiles Private Limited is a world of multi branded Mobile Showroom.

We provide all major brands of mobiles like Nokia, Sony, Samsung, Fly, HTC,

Blackberry, Micromax, Lava, Videocon, Onida, Apple, Celkon, Karbonn & more. We are

also the top provider of Accessories, Memory Card, iPod & Mp3 Player, Travelling

Charger, Data card, Bluetooth and Routers. All brands SIM Card & Recharge available,

Satellite connections like Tata Sky, Airtel DTH, Dish TV.

CUSTOMERS

Poorvika Mobiles is well established in the hearts and minds of the customers due

to maintaining the integrity, quality, honesty and excellent customer service. We focus

more on Customer’s satisfaction and serve customers of all walks of life style. We make

them feel satisfied and comfortable with our range of multi branded products.

We offer the below to maintain our brand successfully,

1. Lowest price,Stock available as per requirement

2. Over 500 products under one roof

3. Long business hours – 10AM – 10PM

4. Quality assured

5. Professional customer care

6. Attractive promotions-Efficient and fast billing-Excellent value of Money -

Ambience

6

Address

# 4 New Scheme Road

ICICI Bank Ground Floor

Pollachi PIN 642002

Email: [email protected]

mailto:[email protected]

7

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

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

8

Proposed system

Advantages of proposed system

2.1EXISTING 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.

Problems in 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.

Need for Proposed System.

Large amount of time is wasted.

Information may does not reach the person properly.

Some information in the existing system may not be true.

9

Duplication of works.

Up to date information is not possible.

Delay in reports.

Lack of accuracy.

2.2PROPOSED SYSTEM

In this all the process are been computerized all the details can be view

and easily it is done by proposed system, so we can view the necessary

information as we expect.

Time is saved; searching of particulars details is very easy like supplier

details, stock details, customer details, purchase details, purchase return

details, sales details, sales return details, machine details.

The project “inventory details” would be really helpful for the Garments

in all the ways.

The storage and retrieval of the data will become easier for the persons in

charge.

Due to technological improvement of computer is very important and

increased the role in human life. Now a day’s all departments are being

computerized.

Benefits of the Proposed System:

Easily understandable design.

Reduce timings.

Minimize cost.

Cool look.

User friendly.

With in short time to view the more details.

Enables the user to get the information about activation at any time, just a

click away.

Facilities to have details with no errors.

10

Reduces the possibility of incoming errors.

Easy accessing and handling.

Helps for updating and modifying the information in an easy way.

2.3 SOFTWARE CONFGURATION

2.3.1 HARDWARE REQUIREMENTS

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 REQUIREMENTS

Operating System : Windows XP (Service pack2)

Front end : VB.Net 2005

Back end : Ms-Access 2003

2.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:

11

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

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

12

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

13

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.

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

14

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

15

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

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.

16

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.

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

17

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

18

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

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.

DataReaders

19

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

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

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

of the returned DataReader object is different from a recordset. For example, you might

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

DataSets and DataAdapters

DataSets

The DataSet object is similar to the ADO Recordset object, but more powerful,

and with one other important distinction: the DataSet 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 DataSet can and does behave

much like a database, it is important to remember that DataSet 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.

DataAdapters (OLEDB/SQL)

The DataAdapter 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

20

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.

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

navigate data relationships

21

MS ACCESS 2003

MS-Access is a powerful database management system and the user can create entire

application that requires little or no programming language VBA that can be used to develop

richer and more developed application. Access is easy enough to use it in a short time and

beginners can learn to manager their own data.

In MS Access, the database means a collection of table that holds data. In collectively

stores all the other related objects, such as queries, forms, and reports. That are use to implement

database managements functions effectively.

The MS Access support the user with it is powerful database very easily using some

mouse clicks.

MS-Access database supports so many data types where a user can incorporate data form

other applications. A database created in MS Access can be accessed through the visual basic

using data control.

Here data base means a collection of related tables and a table means a collection of

numbers of records where a record means a collection of interrelated fields. In a single entity is

used to describe as an attribute.

A single table can have any number of induced files that can be used to locate records

using an expression. This helps in filtering out of information according to specific criteria.

A user can move inside a table very easily using the negative tools supported by the MS

Access database. A table can be accessed in a number of ways like a snapshot, dynasty, table etc.

Microsoft Access has much more sophisticated and easier way to use interface for

creating database object. MS Access support powerful database management functions. MS

Access makes it easy to change existing database structure.

Database:

A database is a repository of information.

Database Engine:

Software that manage how data is stored and retrieved in the database.

Table:

Tables are the main units of data storage in a database. A table is a collection of

data about a specific topic; it is made up of one of more fields.

22

Field:

A field is a column in a table and defines a data type for a set of values in a table.

For example, a mailing list table might include fields for first name, last name, address,

city, state, zip code, and telephone number.

Record:

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

list table, each record would contain the data for one person as specified by the

intersecting fields.

Relationship:

A relationship is a way of defining how two tables relates to each other.

Normalization:

It is concept that is related to relationship. The principle of normalization is that

the database tables will eliminate inconsistence and minimize efficiency. Databases are

inconsistent. When data in one table doesn’t match with the data entered in another table.

Inefficient database doesn’t isolate the exact data you want.

Cost estimation and scheduling:

Software estimation models bearing the name Cocomo for constructive cost

model. The original cocomo model became one of the most widely used and discussed

software cost estimation models in the industry. Cocomo2 is actually a hierarchy of

estimation models that address the following areas.

Application composition model:

Used during the early stages of software engineering, when prototyping of user

interfaces, considerations of software and system. Interactions assessments performance

and evaluation of technology maturity are paramount.

Early design stage model:

Used once requirements have been stabilized and basic software architecture has

been established.

23

Post architecture stage model:

Used during the construction of the software. Like all estimation models for

software, the cocomo2 models require sizing options are available as part of the

hierarchy.

Object points

Function points

Line of severe code

The cocomo2 application composition model uses object points an indirect

software measure that is computed using counts of the number of

Screens

Reports

Components likely to be require to build the application.

Each object instance is classified into one of the complexity levels, complexity is

a function of the number and source of the client and server data tables that are required

to generate the screen or report and the number of views or relations presented as part of

the screen report.

The object point count is then determined by multiplying the original number of

object instances by the weighting factor and summing to obtain a total object point count.

When component bared development or general software require is to be applied, the

percent is estimated and the object print count is adjusted.

Access vs. Excel

Access databases and Excel spreadsheets, although originally very different, have

evolved to have similar functions. Although either type of program can do many, but not

all, of the things that the other one does, there are some things which are easier in one

program than the other.

24

Excel is not a database management system. Excel spreadsheets store data in rows

and columns called worksheets. The areas within the worksheet where the rows and

columns intersect are called cells. The most common use of spreadsheets is to manage

basic information such as telephone numbers, employee names, financial data,

calculations, etc.

Access stores data in tables that look similar to worksheets but function quite

differently. Tables, the foundation of all relational databases, function both independently

and interdependently with other tables to allow the database user to combine data from

multiple sources and analyze and/or report information in almost limitless ways.

25

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

26

3.1.1 DATAFLOW DIAGRAM

LEVEL 0:

Master

Transaction

Mobile

System

Sales details

Counseling details

Jobwork details

Employee details

Customer details

Mobile detail

Service Details

27

LEVEL 1:

User Login

admin Master Entry

Uname, pwd

Mobile

details

Job

work

Customer

Entry

Mobile master

Job work

Cost, tax,

bar no

Customer

Job code, desc,

job char

Employe

e details

Employee

Id, name,

addr,

Cus code,

name, add1,

phone

28

LEVEL 2:

User Login

admin Transaction

Entry

Uname, pwd

counselli

ng

Slaes

details

Service

details

counselling

Sales details

Vehicle code,

name, cusname

Service details

Ser no, job

code, j_desc,

lab_char

Cus code,

name, bill no

29

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.

Login page

Main Form

validation

Database

Sales

Report Customer

report

Employee

Report

Transaction Entry Master entry

custo

mer

showr

oom Emplo

yee

counselling sales service

Vehicle

…………

….

Job

wor

k

30

3.1.3 ER DIAGREM

31

3.2DESIGN PROCESS

3.2.1INPUT 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.

32

The main inputs of the system are

Mobile Module

In this module, we maintain the details about the mobile code, mobile

type, name, engine number, cubic capacity, engine type, head light, danger light, road

tax, color, cost, max weight.

Customer Module

In this module, we maintain the details about the customer code, customer name,

address, phone, mobile number and Email id.

Showroom Module

In this module, we maintain the details about the product code, product name, and

quantity of products.

Employee Module

In this module, we maintain the details about the employee job code, employee

name, employee designation, date of joined, year of experience.

Job work Module

In this module, we maintain the details about the job code, description, change,

date, time.

Counseling Module

In this module, we maintain the details about the customers who are all coming in

to the showroom for enquiry about the mobile.

Sales Module

33

In this module, we maintain the details about bill number, date, customer code,

name, mobile code, name, cost, registration number, registration charges, road tax, extra

fittings, insurance charges, bill amount.

Service Module

In this module, we maintain the details about the service number, service date,

customer code, name, job code, job work charges, description, labour charges, labour

name, total charges, and spare charges

3.2.2OUTPUT 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

Mobile Report



34

Date wise Mobile sales Report

Bill no wise Mobile sales Report


Bill no vehicle service Report

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.

35

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?

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.

36

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.

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.

37

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

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.

38

3.2.3TABLE DESIGN

Table Design

Table name : CusMas

Primary Key: Cuscode

Field name Data type Width Description

Cuscode Varchar 20 Customer code

Name Varchar 20 Customer Name

add1 Varchar 100 Customer address1

add2 Varchar 100 Customer address1

Phone Number 10 Phone number

Mobile Number 10 Mobile number

Mail Varchar 20 Email Id

Reg_No Number 10 Register number

Table name : Job_Work

Primary Key: Job_Code


Job_Code Number 20 Job code

Jod_Desc Varchar 20 Job description

Job_Cha Number 10 Job charges

39

Table name : Ser_Det

Primary Key: J_Code


Ser_No Number 5 Serial number

J_Code Number 20 Job code

J_Desc Varchar 20 Job description

Lab_Cha Number 10 Labour charges

Jo_Char Number 10 Job charges

Total_Char Number 10 Total charges

Table name : Ser_Det

Primary Key: J_Code


Ser_No Number 5 Serial number

Ser_Date Date/time - Date

Cust_Code Varchar 20 Customer code

Cus_Name Varchar 20 Customer name

Spare_Amt Number 10 Spare amount

Bill_Amt Number 10 Bill amount

40

Table name : Mob_Mas

Primary Key: Mob_code


Mob_code Number 5 Mobile Code

Mob_Type Date/time - Mobile Type

Imei_No Varchar 20 IMEI Code

Max_Wt Number 10 Weight

Cost Number 10 Cost

Table name : mob_Sales

Primary Key: mob_code


Bill_No Number 10 Bill number

Bill_Date Date/time - Bill date

Mob_Code Varchar 20 Mobile code

Mob_Name Varchar 20 Mobile name

Mob_Cost Number 10 Mobile cost

Imei_no Varchar 10 Registration number

Tax Number 10 Tax

Extr_Char Number 10 External charges

In_Cha Number 10 Internal charges

Bill_Amt Number 20 Bill amount

41

Sal_Mon Varcahr 10 Sales per month

Sal_Yr Number 10 Sales per year

Cus_Code Varchar 10 Customer code

Cus_Name Varchar 10 Customer name

42

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.

43

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.

44

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.

45

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

46

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.

47

CHAPTER V

5. CONCLUSION

CONCLUSION

The given project is successfully completed and the reports are also generated.

Validation is done accordingly and the system is designed to be as interactive as possible.

Listing them side by side provides all necessary option, any one of the desired option can

be selected and the corresponding operation is performed. Finally the system is

implemented in the client place.

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:

It simplifies the operation.

User friendly screens to enter the data.

Portable and flexible for the future development.

It is fully authenticated.

48

CHAPTERVI

6.FUTURE ENCHANCEMENT

This project is a powerful system .First of all, only authorized users who have

valid password and privilege can run the system. If the user enters the data wrongly, the

system will not allow it to save due to its validation testing; Database is structured with

minimum redundancy.

The system was tested with all possible samples of data and the performance

of the system was proved to be efficient. Thus the system was computerized and all the

drawbacks are rectified and through this the user requirement are fulfilled.

This system is very flexible and changes can be made without much

difficulty. Future Extension in this system can be made to add the feature in internet

advertisements. This System is developed using powerful tools and technology so even

after the development phase, new applications can be applied and integrated very easily

with the existing system.

49

CHAPTER VII

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

“Mastering VB.Net”

Author : EVANGELOS PETROUTOS

Publisher : BPB Publications

“Database Management Systems”

Author : Ramakrishnan

Publisher : Tata Mc.Graw Hill

Edition : Second Edition

“VB.Net Programming”

Author : STEVEN HOLZNER

Publisher : Dreamtech Publication

“Beginning VBNet Database”

Author : THEARON WILLIS

Publisher : Dreamtech Publication

50

Edition : First Edition

WEBPAGE REFERENCES

www.tutorialpoint.com/vb.net/

www.homeandlearn.co.uk/NET/vbnet.html

Howtostartprogramming.com/vb.net

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()

http://www.tutorialpoint.com/vb.net/

http://www.homeandlearn.co.uk/NET/vbnet.html

51

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

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

52

Catch E1 As Exception

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)

txtFax.Text = dr.Item(7)

txtEmail.Text = dr.Item(8)

Else

MsgBox("NotFound")

End If

If Not dr.IsClosed Then dr.Close()

End Sub



53

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

LOGIN FORM

Imports System.Data.sqlclient

Public Class FrmLogin

Inherits System.Windows.Forms.Form

Dim cn As New connectdatabase()

Dim cmd As SqlCommand

Dim dr As SqlDataReader



Try

cn.connect()

' cmd = New sqlCommand("select USERNAME,PASSWORD

from login", conn)

cmd = New SqlCommand()

54

' 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

dr = cmd.ExecuteReader

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

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

55

SAMPLE SCREEN SHOTS

56

57

58

59

60

61

62

63

64

65

66

67

Technology

venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Mobile ne wvijay]