CHAPTER 1

INTRODUCTION
Enterprise Manager allows you to manage your MS SQL Server 2005 database as
well as upload data to it. Before creating the connection to your SQL database ensure you
know your SQL user name and password for you database and also make sure you know
the IP Address of the server your SQL database is located on. This is located in the
HSPHERE Control Panel.
Enterprise Manager is the primary administrative tool for Microsoft SQL Server
2000 and provides a MMCcompliant user interface that allows users to:

Define groups of servers running SQL Server.

Register individual servers in a group.

Configure all SQL Server options for each registered server.

Create and administer all SQL Server databases, objects, logins, users, and
permissions in each registered server.

Define and execute all SQL Server administrative tasks on each registered
server.

Design and test SQL statements, batches, and scripts interactively by

invoking SQL Query Analyzer.

1.1 Objection of the project:

In Order to be able to define our system architecture, we must first dearly
state what our objective that will deliver system behavior at the same one of our
objective is to create an experience, which is not only unique to the (user) client,
but also makes him feel that he has loyal attachment to the system and approaches
us whenever he/she needs.
To achieve better results and success by implement computerized process
instead of manual process.

1.2 Modules and their Description

The project titled Database Enterprise Manger is designed using Active
Server Pages .NET with Microsoft Visual Studio.Net 2008 as front end and Microsoft
SQL Server 2005 as back end which works in .Net framework version 3.5. The coding
language used is C#.Net
The Database enterprise manager contains four main modules. Those modules are
1. Create Connection
2. Create Database
3. Database Manipulation
4. Query Processing
1. Create Connection:
The connection has to be established between server and the running page. That is
the enterprise website page. The connection has to be established by identify the local
host name. If the local host name is not yet to identify put dot in the place of local host
column. Then set the user name and the password. Maximum the user name of the
enterprise manager is sa. These securities are set for preventing the database from Crash
or memory leakage.

2. Create Database:
After connection establishment, the user has to create the database for their
purpose. This can be done in the way of click the database properties, then the database
properties windows open. In that window, give the database name as we want. The size,
growth, max size is set as default. After enter the name in the database name click the
save login button. Then the database is created for that user with the specified name. The
table properties such as tables, views, stored procedures, users, roles are generated as
default.

3. Database Manipulation:
Extensive data manipulation facilities for creating, copying, moving, converting
reformatting and validating application test data are essential for the efficient
development of reliable z/OS applications.
The same facilities are also essential in addressing failures in live systems, where
it is imperative to find and fix production data errors with confidence and precision.
1. Data Manipulation is:
o retrieval of information from the database
o

insertion of new information into the database

deletion of information in the database

modification of information in the database

2. A DML is a language which enables users to access and manipulate data. The goal
is to provide efficient human interaction with the system.
3. There are two types of DML:
o procedural: the user specifies what data is needed and how to get it
o

nonprocedural: the user only specifies what data is needed

Easier for user

May not generate code as efficient as that produced by procedural

languages

4. A query language is a portion of a DML involving information retrieval only. The

terms DML and query language are often used synonymously.

3.1. Insert Command

This command is used to add rows to a table. The format:
INSERT INTO table
Values (list of values separated by commas).
INSERT INTO table
Select statement that retrieves values from another table
INSERT INTO Patron
Values (100, 'Marsha', 'F')

Note that the default format for dates is day-month-year, where month is a three
digit character abbreviation. The date should be between single quotes (e.g., 20JUL-95).

3.2. Delete Command

This command removes rows from a table. The format:
DELETE FROM table name
Where condition
DELETE FROM Patron
Where PID = 100

3.3. Update Command

This command changes data in one or more rows
UPDATE tablename
SET attributename = some expression (can be an equation)
Where condition
Note that you can have more than one set statement per UPDATE command.
UPDATE Checkout
SET DueDate = '10-Dec-95'
Where PID = 100

4. Query Processing:
Select Query
The select query used in Oracle is standard SQL so you should look in your text
book for syntax and examples. The following sections illustrate some capabilities or
syntax variations in Oracle that are not in the text.

Outer Joins
Unlike Outer Joins in the text, outer joins in Oracle are declared in the Where
clause through the use of the (+) symbol. An example follows:
Select b.title, c.pid
From Book b, Checkout c
Where b.callno = (+) c.callno

The =(+) says to join the book callno with the checkout callno. But if there is no
checkout callno to match book callno, use a null in the checkout attributes. Notice that
the above example would be considered a left outer join in our book even though the (+)
is to the right of the equal sign.

Special Set Operators

Oracle supports union, intersect and minus set operations on two select
statements.

The System Catalog

Oracle keeps the names of your tables and other information in a Meta table
called user tables. To see this information, use a simple select statement. The following
statement lists the table names:
Select TABLE_NAME from USER_TABLES;

To find out all the information on your tables, type:

Select * from USER_TABLES;

Group Functions
Oracle supports the following group functions in a SQL query:

AVG -- average
COUNT
MAX -- Returns the maximum value
MIN -- Returns the minimum value
STDDEV -- Standard Deviation
SUM -- The total of some column
VARIANCE

All of the above can be used with the DISTINCT option

CHAPTER 2

SOFTWARE PROJECT PLAN

This chapter discusses about that time schedule for the project and it contain the
various phases of the project.

The Various Phases of the Project:

S.NO

TASK

DURATION

REQUIREMENT

10 DAYS

SPECIFICATION
REQUIREMENT

10 DAYS

DOCUMENT SPECIFICATION
3

DESIGN ANALYSIS

20 DAYS

DESIGN

15 DAYS

5
6

DOCUMENTATION
DESIGN REVIEW

20 DAYS

CODING

15 DAYS

TOTAL

90 DAYS

CHAPTER 3

CUSTOMER REQUIREMENTS DETERMINATION

3.1 Existing System
Microsoft SQL Server, a specific relational database management system
(RDBMS) from Microsoft .Sybase SQL Server, a DBMS developed by Sybase (and, for a
period, jointly with Microsoft) that was the predecessor to Sybase Adaptive Server
Enterprise and Microsoft SQL Server. SQL Server Magazine, a publication of Penton
Media. Less commonly, any DBMS that implements the SQL query language
3.2 Proposed System

The database manager is a program module which provides the

interface between the low-level data stored in the database and the application programs
and queries submitted to the system.
Databases typically require lots of storage space (gigabytes). This must be
stored on disks. Data is moved between disk and main memory (MM) as needed.
The goal of the database system is to simplify and facilitate access to
data. Performance is important. Views provide simplification.
So the database manager module is responsible for
Interaction with the file manager: Storing raw data on disk using the file
system usually provided by a conventional operating system. The database manager must
translate DML statements into low-level file system commands (for storing, retrieving
and updating data in the database).
Integrity enforcement: Checking that updates in the database do not
violate consistency constraints (e.g. no bank account balance below $25)
Security enforcement: Ensuring that users only have access to
information they are permitted to see

Backup and recovery: Detecting failures due to power failure, disk crash,
software errors, etc., and restoring the database to its state before the failure
Concurrency control: Preserving data consistency when there are
concurrent users.
Some small database systems may miss some of these features, resulting
in simpler database managers. (For example, no concurrency is required on a PC running
MS-DOS.) These features are necessary on larger systems.

CHAPTER 4
SOFTWARE REQUIREMENTS SPECIFICATION

Software Requirements Specification (SRS) is the starting point of the

software development activity. Little importance was given to this phases in the early
days of software development. The emphasis was first on coding and then shifted to
design.
As systems grew more complex, it become evident that the goal of the
entire system cannot be easily comprehended. Hence need for the requirements analysis
phase arose. Now, for large software systems, requirements analysis is perhaps the most
difficult activity and also the most error prone.
Some of the difficulty is due to the scope of this phase. The software
project is imitated by the client needs. In the beginning these needs are in the minds of
various people in the client organization. The requirement analyst has to identify the
requirements by tacking to these people and understanding there needs. In situations
where the software is to automated a currently manuals process, most of the needs can be
understood by observing the current practice.
The SRS is a means of translating the ideas in the minds of the clients (the
output) into formal document (the output of the requirements phase). Thus the output of
the phase is a set of formally specified requirements, which hopefully are complete and
consistent, while the input has none of these properties.

4.1 Fuctional Requirements

Connection
Special
Operator

Create Connection

Group
Joins

functio
n

Database
Query

Create Database

Enterpris

Processing

e
Manager

Databas
e

Database
Manipulation
DML

Insert

Delet
e

4.2 Performance Requirements

Update

Select

The project must the end user requirements. Accuracy and fast must be imposed
in the Project.
The project is development as easy as possible for the sake of end user. The
project has to be developed with view of satisfying the future requirements and future
enhancement.
This processing as well as tine taken to generate well reports where also even
when large amount of data was used. The system is designed in such a way that even
when large amount of data used for processing there would less performance degradation.

4.3 Interface requirements

4.3.1 Hardware Interface
The stranded input device like keyboard and mouse are to get input. The output
will be generated and display in the monitor. The reports can also be exported to a SQLserver document are text file. The stranded printer in used to take outputs.
4.3.2 Software Interface
The design part and interface id done the front end ASP.Net and SQL server as a
backend of the project.

4.4 Operational requirements

The database or databases that are being failed over to the stand by server cannot
be used for anything else. but databases on the standby server not being used for failover
can still be used normally.
When it comes time for actual failover, you much one of two things to
make your application work either rename the standby server the same name as the
failed production server(and the IP address),or re-point your users applications to new
standby server in some cases,neither of this option is practical

4.5 Resource Requirements

4.5.1 Hardware Requirements

PROCESSOR

PENTIUM III 866 MHz

RAM

128 MD SD RAM

MONITOR

15 COLOR

HARD DISK

20 GB

FLOPPY DRIVE

1.44 MB

CD DRIVE

LG 52X

KEYBOARD

STANDARD 102 KEYS

MOUSE

3 BUTTONS

4.5.2 Software Requirements

OPERATING SYSTEM

Windows XP Professional

ENVIRONMENT

Visual Studio .NET 2008

.NET FRAMEWORK

Version 3.5

LANGUAGE

C#.NET

WEB TECHNOLOGY
BACKEND

ASP.NET
:

SQL SERVER 2005

4.6 Security Requirements

Web application are available via network access, it is a difficult. If not possible,
to limit the population of the end-user who may access the applications? In order to
product sensitive connect and provide secure mode be implemented throughout the
infrastructure that the supports web application and within the application itself.
Web Application have become heavy integrated with critical corporate and
database.
E-commerce application extracts and then store sensitive customer information.

4.7 Design Requirements

To create project, add base masters and masters to the project,

assign behaviors to the master, create and assign behavior sets, and then apply, test and
validate those behaviors. It also shows how to create and build a stencil to hold the
shapes.

4.8 Quality and Reliability Requirements

A software component that is developed for reuse would be correct and would
contain no defects. In reality, formal verification is not carried out routinely, and defects
can add to occur.However, with each reuse,defects are found eliminated, and a
components qualify improve as a result. Over time the components virtually defect free.
Software reliability is defined in statical term as the probability of faultier-free
operation of a computer program in a specified environment for specified tine. The
software quality and reliability, failure is nonconformance to software requirements.
Failure can be only anything or catastrophic. one failure can be corrected within seconds
while another requirements week even mouths to correct. Complicating the issue even
further, the correction of the one failure may in fact result in the introduction of the errors
that ultimately result in other failure.
Web
Application
Quality

Correct link processing

Reliability

Error recovery
Input validation and recovery

CHAPTER 5

SYSTEM ANALYSIS
In this section discussed about data flow diagram, Entity relationship
diagram. These things are represented as diagrams with proper notation.
5.1 Data Flow Diagram
The data flow diagram is one of the most improvement tools used by the
system analyst DeMacro (1978) Nad Gand Sarson (1979) popularized the use if the data
flow diagram as modeling tools through their structured system analysis methodologies.
A data flow diagram should be the first tool used by system analyst to
model system components. These components are the system processes; the data used by
this processes and external entities that interact

with the system and the information

flows in the system.

There are four kinds of system components
5.1.1. Process
Process show what system does. Each process has one or more data inputs
and produce one or more data output, Circles in a data flow diagram represent process.
Each process has unique name and number. This name and number appear inside the
circle that represents the processes in a data flow diagram.
This process is represented as circle

5.1.2. Data Stores:

File or data store is depositary of data. They contain data that is

retained in the system. Processes can enter the data into a data store or retrieve data from
the data store. Each data store is represented by thin line in the data flow diagram and
each data store has a unique name.
The data store is represented in form of a line

5.1.2 External Entities:

External entities are outside the system but they either supply input
data into the system or use the system output, they are entities which the designer has no
control. Square or rectangle may represent external entities that supply data into a system
or some times called sources. External entities that use the system data are sometimes
called sinks.

5.1.4 Data Flows:

Dataflow model the passage of data in the system and are represented lines
joining system components. An arrow indicates the direction of the flow and the line
labeled by the name of the data flow.

5.2 ER DIAGRAM

Connection
Special
Operator

Create Connection

Group
Joins

functio
n

Database
Query

Create Database

Enterpris

Processing

e
Manager

Databas
e

Database
Manipulation
DML

Insert

Delet

Update

Select

Novice user

application programmer

sophisticate user

database administrator

Application

Application

usercase

program

query

scheme

Xml

Xml

Query

precompiler

processor

compiler

Database

Application
program

Database

object

manager

code

File manager

datafiles

Data
directory
Disk storage

5.3 Software development life cycle

Title

Authorization

Submission

Certificate

Students
DB

Learning

Training

Process

Problem Analysis:
DATABASE ENTERPRISE
MANAGER
Authorization
Signatory
Front-end Asp.net
Back-end: SQL Server

Networking Design:
Internet Explorer 6.0

Coding

Validation

Testing

Document

Reports

nnn

Certificate

Complete Certificate

ProgrammerTraining
Certificate

CHAPTER 6

SYSTEM DESIGN
Design is multi-step process that focuses on data structure software
architecture, procedural details, (algorithms etc.) and interface between modules.
The design process also translates the requirements into the presentation of
software that can be accessed for quality before coding begins.
Computer software design changes continuously as new methods; better
analysis and broader understanding evolved. Software Design is at relatively early
stage in its revolution.
Therefore, Software Design methodology lacks the depth, flexibility and
quantitative nature that are normally associated with more classical engineering
disciplines. However techniques for software designs do exist, criteria for design
qualities are available and design notation can be applied.

6.1 INPUT DESIGN

Input design is the process of converting user-originated inputs to a
computer-based format. Input design is one of the most expensive phases of the
operation of computerized system and is often the major problem of a system.
In the project, the input design is made in various web forms with
various methods. For example, in the Admin form, the empty username and
password is not allowed. The username if exists in the database, the input is
considered to be invalid and is not accepted.
6.2 OUTPUT DESIGN
Output design generally refers to the results and information that
are generated by the system for many end-users; output is the main reason for

developing the system and the basis on which they evaluate the usefulness of the
application.
In the project, if the employee has to communicate with other employees
they can communicate through send and receive message.
6.3 INTERFACE DESIGN
The ODBC (Open Database Connectivity) interface is a pure .NET to
execute SQl statement. The ODBC provides a set classes and interfaces that can
be used by developers to write database applications. Basic ODBC interactions in
its simplest form, can be broken down into four steps:
1. Open a connection to the database.
2. Execute a SQL statement
3. Process the result
4. Close the connection to the database

6.4 TABLE AND DATABASE DESIGN:

6.4.1 Normalization:
Normalization is the process of strutting relational database schema such that
most ambiguity is removed. The stage of normalization are referred to as forms and
progress from the least restrictive(first normal form)through the most restrictive(Fifth
normal form), generally , most database designers do not attempt to implement anything
higher then normal form of Boyce code Normal Form.
6.4.1.1FIRST NORMAL FORM:
A relation is said to be in First normal form (INF) if and each attributed of
the relation is atomic. More simply, to be INF, each column must contain only a single
value and each now contain in the same column.
6.4.1.2 SECOND NORMAL FORM:
In the Second normal Form, a relation must first fulfill the requirement to be in
first Normal Form. Additional, each donkey attribute in the relation must be functionality
dependent upon the primary key.

6.4.1.3 THIRD NORMAL FORM:

A table is said to be in third normal form and every non key attribute is
functionality dependent only on the primary key. This normalization process is applied to
this system and the normalized tables are given in the above section.

6.4.2 Database Design:

The database design is a must for any application developed especially
more for the data store projects. Since the chatting method involves storing the
message in the table and produced to the sender and receiver, proper handling of
the table is a must.
In the project, login table is designed to be unique in accepting the
username and the length of the username and password should be greater than
zero
The complete listing of the tables and their fields are provided in the
annexure under the title Table Structure

6.5 FRONT END DESIGN

6.1 Features Of Asp .Net
The .Net Framework
The .NET Framework is a new computing platform that simplifies application
development in the highly distributed environment of the Internet.
Objectives of .net framework:
1. To provide a consistent object-oriented programming environment whether
object codes is stored and executed locally on Internet-distributed, or executed remotely.
2. To provide a code-execution environment to minimizes software deployment
and guarantees safe execution of code.
3. Eliminates the performance problems.
There are different types of application, such as Windows-based applications and
Web-based applications. To make communication on distributed environment to ensure
that code be accessed by the .NET Framework can integrate with any other code.

COMPONENTS OF . NET FRAMEWORK

1. The Common Language Runtime (CLR):
The common language runtime is the foundation of the .NET Framework. It
manages code at execution time, providing important services such as memory
management, thread management, and remoting and also ensures more security and
robustness. 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 .net frame work class library:
It is a comprehensive, object-oriented collection of reusable
types used 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 unmanaged features. The .NET Framework not only provides several runtime hosts,
but also supports the development of third-party runtime hosts.
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 to enables embeds managed components or Windows Forms controls in
HTML documents.

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 are all run on CLR.
Security.
Robustness.
Productivity.
Performance.
SECURITY
The runtime enforces code access security. The security features of the
runtime thus enable legitimate Internet-deployed software to be exceptionally feature
rich. With regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin to perform file-access
operations, registry-access operations, or other sensitive functions.
ROBUSTNESS:
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 managed environment of the
runtime eliminates many common software issues.
PRODUCTIVITY:
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.
PERFORMANCE:
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. Finally, the

runtime can be hosted by high-performance, server-side applications, such as Microsoft

SQL Server and Internet Information Services (IIS).
ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified
Web development platform that provides the services necessary for developers to build
enterprise-class Web applications. While ASP.NET is largely syntax compatible, it also
provides a new programming model and infrastructure for more secure, scalable, and
stable applications.
ASP.NET is a compiled, NET-based environment, we can author
applications in any .NET compatible language, including Visual Basic .NET, C#, and
JScript .NET. Additionally, the entire .NET Framework is available to any ASP.NET
application. Developers can easily access the benefits of these technologies, which
include the managed common language runtime environment (CLR), type safety,
inheritance, and so on.
ASP.NET has been designed to work seamlessly with WYSIWYG HTML
editors and other programming tools, including Microsoft Visual Studio .NET. Not only
does this make Web development easier, but it also provides all the benefits that these
tools have to offer, including a GUI that developers can use to drop server controls onto a
Web page and fully integrated debugging support.
Developers can choose from the following two features when creating an
ASP.NET application. Web Forms and Web services, or combine these in any way they
see fit. Each is supported by the same infrastructure that allows you to use authentication
schemes, cache frequently used data, or customize your application's configuration, to
name only a few possibilities.
Web Forms allows us to build powerful forms-based Web pages. When building
these pages, we can use ASP.NET server controls to create common UI elements, and
program them for common tasks. These controls allow we to rapidly build a Web Form
out of reusable built-in or custom components, simplifying the code of a page.
An XML Web service provides the means to access server functionality
remotely. Using Web services, businesses can expose programmatic interfaces to their

data or business logic, which in turn can be obtained and manipulated by client and server
applications. XML Web services enable the exchange of data in client-server or serverserver scenarios, using standards like HTTP and XML messaging to move data across
firewalls. XML Web services are not tied to a particular component technology or objectcalling convention. As a result, programs written in any language, using any component
model, and running on any operating system can access XML Web services
Each of these models can take full advantage of all ASP.NET features,
as well as the power of the .NET Framework and .NET Framework common language
runtime.
Accessing databases from ASP.NET applications is an often-used
technique for displaying data to Web site visitors. ASP.NET makes it easier than ever to
access databases for this purpose. It also allows us to manage the database from your
code .
ASP.NET provides a simple model that enables Web developers to
write logic that runs at the application level. Developers can write this code in the
global.aspx text file or in a compiled class deployed as an assembly. This logic can
include application-level events, but developers can easily extend this model to suit the
needs of their Web application.
ASP.NET provides easy-to-use application and session-state facilities
that are familiar to ASP developers and are readily compatible with all other .NET
Framework APIs.
ASP.NET offers the IHttpHandler and IHttpModule interfaces.
Implementing the IHttpHandler interface gives you a means of interacting with the lowlevel request and response services of the IIS Web server and provides functionality much
like ISAPI extensions, but with a simpler programming model. Implementing the
IHttpModule interface allows you to include custom events that participate in every
request made to your application.
ASP.NET takes advantage of performance enhancements found in
the .NET Framework and common language runtime. Additionally, it has been designed
to offer significant performance improvements over ASP and other Web development
platforms. All ASP.NET code is compiled, rather than interpreted, which allows early

binding, strong typing, and just-in-time (JIT) compilation to native code, to name only a
few of its benefits. ASP.NET is also easily factorable, meaning that developers can
remove modules (a session module, for instance) that are not relevant to the application
they are developing.
ASP.NET provides extensive caching services (both built-in services and
caching APIs). ASP.NET also ships with performance counters that developers and
system administrators can monitor to test new applications and gather metrics on existing
applications.
Writing custom debug statements to your Web page can help immensely in
troubleshooting your application's code. However, it can cause embarrassment if it is not
removed. The problem is that removing the debug statements from your pages when your
application is ready to be ported to a production server can require significant effort.
ASP.NET offers the TraceContext class, which allows us to write custom
debug statements to our pages as we develop them. They appear only when you have
enabled tracing for a page or entire application. Enabling tracing also appends details
about a request to the page, or, if you so specify, to a custom trace viewer that is stored in
the root directory of your application.
The .NET Framework and ASP.NET provide default authorization and
authentication schemes for Web applications. we can easily remove, add to, or replace
these schemes, depending upon the needs of our application .
ASP.NET configuration settings are stored in XML-based files, which are
human readable and writable. Each of our applications can have a distinct configuration
file and we can extend the configuration scheme to suit our requirements.

6.6 BACK-END DESIGN

4.2 Features Of Sql-Server
The OLAP Services feature available in SQL Server version 7.0 is now
called SQL Server 2000 Analysis Services. The term OLAP Services has been replaced
with the term Analysis Services. Analysis Services also includes a new data mining
component. The Repository component available in SQL Server version 7.0 is now called

Microsoft SQL Server 2000 Meta Data Services. References to the component now use
the term Meta Data Services. The term repository is used only in reference to the
repository engine within Meta Data Service.
SQL-SERVER database consist of six type of objects,
They are,
1. TABLE
2. QUERY
3. FORM
4. REPORT
5. MACRO
TABLE:
A database is a collection of data about a specific topic.
VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet View
Design View
To build or modify the structure of a table we work in the table design view. We
can specify what kind of data will be hold.
Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view mode.
QUERY:
A query is a question that has to be asked the data. Access gathers data that
answers the question from one or more table. The data that make up the answer is either
dynaset (if you edit it) or a snapshot(it cannot be edited).Each time we run query, we get
latest information in the dynaset.Access either displays the dynaset or snapshot for us to
view or perform an action on it ,such as deleting or updating.

FORMS:
A form is used to view and edit information in the database record by record .A
form displays only the information we want to see in the way we want to see it. Forms
use the familiar controls such as textboxes and checkboxes. This makes viewing and
entering data easy.
Views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View
Design View
To build or modify the structure of a form, we work in forms design
view. We can add control to the form that are bound to fields in a table or query, includes
textboxes, option buttons, graphs and pictures.
Form View
The form view which display the whole design of the form.
REPORT:
A report is used to vies and print information from the database. The report
can ground records into many levels and compute totals and average by checking values
from many records at once. Also the report is attractive and distinctive because we have
control over the size and appearance of it.
MACRO:
A macro is a set of actions. Each action in macros does something. Such
as opening a form or printing a report .We write macros to automate the common tasks
the work easy and save the time.
MODULE:
Modules are units of code written in access basic language. We can write
and use module to automate and customize the database in very sophisticated ways.

CHAPTER 7
CODINGS
using System;
using System.Drawing;
using System.Collections;
using System.ComponentModel;
using System.Windows.Forms;
using System.Data;
namespace QueryGenerator
{
/// <summary>
/// Summary description for Form1.
/// </summary>
public class frmMain : System.Windows.Forms.Form
{
private System.Windows.Forms.TextBox txtTableName;
private System.Windows.Forms.TextBox txtColumnNo;
private System.Windows.Forms.Button btnReload;
private int no = 0;
private ucColumn[] colList;
private System.Windows.Forms.Button btnGenerateQueries;
private System.Windows.Forms.TextBox txtInsertQuery;
private System.Windows.Forms.TextBox txtUpdateQuery;
private System.Windows.Forms.TextBox txtDeleteQuery;
private System.Windows.Forms.Button btnCopyInsert;
private System.Windows.Forms.Button btnCopyUpdate;
private System.Windows.Forms.Button btnCopyDelete;
private System.Windows.Forms.Label lblTableName;
private System.Windows.Forms.Label lblColumnNo;

private System.Windows.Forms.Label lblPrimary;

private System.Windows.Forms.Label lblColName;
private System.Windows.Forms.Label lblDataType;
private System.Windows.Forms.Label lblSize;
private System.Windows.Forms.Label lblAllowNulls;
private System.Windows.Forms.Label lblInsertQuery;
private System.Windows.Forms.Label lblUpdateQuery;
private System.Windows.Forms.Label lblDeleteQuery;
private System.Windows.Forms.Button btnClose;
/// <summary>
/// Required designer variable.
/// </summary>
private System.ComponentModel.Container components = null;
public frmMain()
{
//
// Required for Windows Form Designer support
//
InitializeComponent();
//
// TODO: Add any constructor code after
InitializeComponent call
//
}
/// <summary>
/// Clean up any resources being used.
/// </summary>
protected override void Dispose( bool disposing )
{
if( disposing )
{
if (components != null)
{
components.Dispose();
}

}
base.Dispose( disposing );
}
#region Windows Form Designer generated code
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
this.lblTableName = new System.Windows.Forms.Label();
this.txtTableName = new System.Windows.Forms.TextBox();
this.txtColumnNo = new System.Windows.Forms.TextBox();
this.lblColumnNo = new System.Windows.Forms.Label();
this.btnReload = new System.Windows.Forms.Button();
this.lblPrimary = new System.Windows.Forms.Label();
this.lblColName = new System.Windows.Forms.Label();
this.lblDataType = new System.Windows.Forms.Label();
this.lblSize = new System.Windows.Forms.Label();
this.lblAllowNulls = new System.Windows.Forms.Label();
this.btnGenerateQueries = new System.Windows.Forms.Button();
this.lblInsertQuery = new System.Windows.Forms.Label();
this.txtInsertQuery = new System.Windows.Forms.TextBox();
this.btnCopyInsert = new System.Windows.Forms.Button();
this.btnCopyUpdate = new System.Windows.Forms.Button();
this.txtUpdateQuery = new System.Windows.Forms.TextBox();
this.lblUpdateQuery = new System.Windows.Forms.Label();
this.btnCopyDelete = new System.Windows.Forms.Button();
this.txtDeleteQuery = new System.Windows.Forms.TextBox();
this.lblDeleteQuery = new System.Windows.Forms.Label();
this.btnClose = new System.Windows.Forms.Button();
this.SuspendLayout();
//
// lblTableName
//
this.lblTableName.Location = new System.Drawing.Point(8, 8);
this.lblTableName.Name = "lblTableName";

this.lblTableName.Size = new System.Drawing.Size(80, 16);

this.lblTableName.TabIndex = 0;
this.lblTableName.Text = "Table name";
//
// txtTableName
//
this.txtTableName.Location = new System.Drawing.Point(8,
24);
this.txtTableName.Name = "txtTableName";
this.txtTableName.Size = new System.Drawing.Size(184, 21);
this.txtTableName.TabIndex = 1;
//
// txtColumnNo
//
this.txtColumnNo.Location = new System.Drawing.Point(208,
24);
this.txtColumnNo.Name = "txtColumnNo";
this.txtColumnNo.Size = new System.Drawing.Size(72, 21);
this.txtColumnNo.TabIndex = 3;
this.txtColumnNo.TextAlign =
System.Windows.Forms.HorizontalAlignment.Right;
//
// lblColumnNo
//
this.lblColumnNo.Location = new System.Drawing.Point(208,
8);
this.lblColumnNo.Name = "lblColumnNo";
this.lblColumnNo.Size = new System.Drawing.Size(80, 16);
this.lblColumnNo.TabIndex = 2;
this.lblColumnNo.Text = "No of columns";
//
// btnReload
//
this.btnReload.Location = new System.Drawing.Point(304, 24);
this.btnReload.Name = "btnReload";
this.btnReload.Size = new System.Drawing.Size(112, 24);
this.btnReload.TabIndex = 4;
this.btnReload.Text = "Reload";

this.btnReload.Click += new
System.EventHandler(this.btnReload_Click);
//
// lblPrimary
//
this.lblPrimary.Location = new System.Drawing.Point(8, 72);
this.lblPrimary.Name = "lblPrimary";
this.lblPrimary.Size = new System.Drawing.Size(48, 16);
this.lblPrimary.TabIndex = 5;
this.lblPrimary.Text = "Primary";
//
// lblColName
//
this.lblColName.Location = new System.Drawing.Point(56, 72);
this.lblColName.Name = "lblColName";
this.lblColName.Size = new System.Drawing.Size(80, 16);
this.lblColName.TabIndex = 6;
this.lblColName.Text = "Column name";
//
// lblDataType
//
this.lblDataType.Location = new System.Drawing.Point(216,
72);
this.lblDataType.Name = "lblDataType";
this.lblDataType.Size = new System.Drawing.Size(56, 16);
this.lblDataType.TabIndex = 7;
this.lblDataType.Text = "Data type";
//
// lblSize
//
this.lblSize.Location = new System.Drawing.Point(320, 72);
this.lblSize.Name = "lblSize";
this.lblSize.Size = new System.Drawing.Size(24, 16);
this.lblSize.TabIndex = 8;
this.lblSize.Text = "Size";
//
// lblAllowNulls
//

this.lblAllowNulls.Location = new System.Drawing.Point(384,

72);
this.lblAllowNulls.Name = "lblAllowNulls";
this.lblAllowNulls.Size = new System.Drawing.Size(64, 16);
this.lblAllowNulls.TabIndex = 9;
this.lblAllowNulls.Text = "Allow nulls";
//
// btnGenerateQueries
//
this.btnGenerateQueries.Location = new
System.Drawing.Point(480, 24);
this.btnGenerateQueries.Name = "btnGenerateQueries";
this.btnGenerateQueries.Size = new System.Drawing.Size(112,
24);
this.btnGenerateQueries.TabIndex = 10;
this.btnGenerateQueries.Text = "Generate queries";
this.btnGenerateQueries.Click += new
System.EventHandler(this.btnGenerateQueries_Click);
//
// lblInsertQuery
//
this.lblInsertQuery.Location = new System.Drawing.Point(480,
72);
this.lblInsertQuery.Name = "lblInsertQuery";
this.lblInsertQuery.Size = new System.Drawing.Size(80, 16);
this.lblInsertQuery.TabIndex = 11;
this.lblInsertQuery.Text = "Insert query";
//
// txtInsertQuery
//
this.txtInsertQuery.Location = new System.Drawing.Point(480,
88);
this.txtInsertQuery.Multiline = true;
this.txtInsertQuery.Name = "txtInsertQuery";
this.txtInsertQuery.ScrollBars =
System.Windows.Forms.ScrollBars.Both;
this.txtInsertQuery.Size = new System.Drawing.Size(392,
128);

this.txtInsertQuery.TabIndex = 12;
//
// btnCopyInsert
//
this.btnCopyInsert.Location = new System.Drawing.Point(760,
224);
this.btnCopyInsert.Name = "btnCopyInsert";
this.btnCopyInsert.Size = new System.Drawing.Size(112, 24);
this.btnCopyInsert.TabIndex = 13;
this.btnCopyInsert.Text = "Copy to clipboard";
this.btnCopyInsert.Click += new
System.EventHandler(this.btnCopyInsert_Click);
//
// btnCopyUpdate
//
this.btnCopyUpdate.Location = new System.Drawing.Point(760,
400);
this.btnCopyUpdate.Name = "btnCopyUpdate";
this.btnCopyUpdate.Size = new System.Drawing.Size(112, 24);
this.btnCopyUpdate.TabIndex = 16;
this.btnCopyUpdate.Text = "Copy to clipboard";
this.btnCopyUpdate.Click += new
System.EventHandler(this.btnCopyUpdate_Click);
//
// txtUpdateQuery
//
this.txtUpdateQuery.Location = new System.Drawing.Point(480,
264);
this.txtUpdateQuery.Multiline = true;
this.txtUpdateQuery.Name = "txtUpdateQuery";
this.txtUpdateQuery.ScrollBars =
System.Windows.Forms.ScrollBars.Both;
this.txtUpdateQuery.Size = new System.Drawing.Size(392,
128);
this.txtUpdateQuery.TabIndex = 15;
//
// lblUpdateQuery
//

this.lblUpdateQuery.Location = new System.Drawing.Point(480,

248);
this.lblUpdateQuery.Name = "lblUpdateQuery";
this.lblUpdateQuery.Size = new System.Drawing.Size(80, 16);
this.lblUpdateQuery.TabIndex = 14;
this.lblUpdateQuery.Text = "Update query";
//
// btnCopyDelete
//
this.btnCopyDelete.Location = new System.Drawing.Point(760,
576);
this.btnCopyDelete.Name = "btnCopyDelete";
this.btnCopyDelete.Size = new System.Drawing.Size(112, 24);
this.btnCopyDelete.TabIndex = 19;
this.btnCopyDelete.Text = "Copy to clipboard";
this.btnCopyDelete.Click += new
System.EventHandler(this.btnCopyDelete_Click);
//
// txtDeleteQuery
//
this.txtDeleteQuery.Location = new System.Drawing.Point(480,
440);
this.txtDeleteQuery.Multiline = true;
this.txtDeleteQuery.Name = "txtDeleteQuery";
this.txtDeleteQuery.ScrollBars =
System.Windows.Forms.ScrollBars.Both;
this.txtDeleteQuery.Size = new System.Drawing.Size(392,
128);
this.txtDeleteQuery.TabIndex = 18;
//
// lblDeleteQuery
//
this.lblDeleteQuery.Location = new System.Drawing.Point(480,
424);
this.lblDeleteQuery.Name = "lblDeleteQuery";
this.lblDeleteQuery.Size = new System.Drawing.Size(80, 16);
this.lblDeleteQuery.TabIndex = 17;
this.lblDeleteQuery.Text = "Delete query";

//
// btnClose
//
this.btnClose.Location = new System.Drawing.Point(752, 24);
this.btnClose.Name = "btnClose";
this.btnClose.Size = new System.Drawing.Size(112, 24);
this.btnClose.TabIndex = 20;
this.btnClose.Text = "Close";
this.btnClose.Click += new
System.EventHandler(this.btnClose_Click);
//
// frmMain
//
this.AutoScaleBaseSize = new System.Drawing.Size(5, 14);
this.ClientSize = new System.Drawing.Size(880, 613);
this.Controls.Add(this.btnClose);
this.Controls.Add(this.btnCopyDelete);
this.Controls.Add(this.txtDeleteQuery);
this.Controls.Add(this.lblDeleteQuery);
this.Controls.Add(this.btnCopyUpdate);
this.Controls.Add(this.txtUpdateQuery);
this.Controls.Add(this.lblUpdateQuery);
this.Controls.Add(this.btnCopyInsert);
this.Controls.Add(this.txtInsertQuery);
this.Controls.Add(this.lblInsertQuery);
this.Controls.Add(this.btnGenerateQueries);
this.Controls.Add(this.lblAllowNulls);
this.Controls.Add(this.lblSize);
this.Controls.Add(this.lblDataType);
this.Controls.Add(this.lblColName);
this.Controls.Add(this.lblPrimary);
this.Controls.Add(this.btnReload);
this.Controls.Add(this.txtColumnNo);
this.Controls.Add(this.lblColumnNo);
this.Controls.Add(this.txtTableName);
this.Controls.Add(this.lblTableName);

this.Font = new System.Drawing.Font("Tahoma", 8.25F,

System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point,
((byte)(0)));
this.Name = "frmMain";
this.StartPosition =
System.Windows.Forms.FormStartPosition.CenterScreen;
this.Text = "SQL Query Generator";
this.Load += new System.EventHandler(this.frmMain_Load);
this.ResumeLayout(false);
this.PerformLayout();
}
#endregion
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main()
{
Application.Run(new frmMain());
}
private void btnReload_Click(object sender, System.EventArgs
e)
{
try
{
for(int i = 0; i<no; i++) colList[i].Dispose();
no = Convert.ToInt32(txtColumnNo.Text);
colList = new ucColumn[no];
for(int i = 0; i<no; i++)
{
colList[i] = new ucColumn();
colList[i].Location = new
System.Drawing.Point(8, 90+i*28);

colList[i].Size = new
System.Drawing.Size(432, 21);
this.Controls.Add(colList[i]);
}
}
catch(Exception ex)
{
MessageBox.Show("Please type valid integer for
number of columns.","Error",MessageBoxButtons.OK,MessageBoxIcon.Error);
}
}
private string createtype(string size)
{
if(size != "") return "("+size+")"; else return "";
}
public string allownull(string logic)
{
if(logic=="Yes") return "=NULL"; else return "";
}
private string checkvalidity()
{
for(int i=0; i<no; i++)
if(colList[i].txtSize.Text !="" )
try
{

Convert.ToInt32(colList[i].txtSize.Text);
}
catch(Exception x)
{
return "Wrong size entered for
field: "+colList[i].txtColumn.Text;
}
return "";

}
private bool checkforprimary()
{
bool check = false;
for(int i=0; i<no; i++)
if(colList[i].chbPrimary.Checked) check = true;
return check;
}
private void btnGenerateQueries_Click(object sender,
System.EventArgs e)
{
if(checkvalidity()=="")
{
if((no > 0) && (txtTableName.Text != ""))
{
txtInsertQuery.Text = "CREATE PROCEDURE
dbo.sp_Insert_"+txtTableName.Text;
txtInsertQuery.Text += "\r\n(";
if(no>1)
{
for(int i=0;i<no-1;i++)
txtInsertQuery.Text += "\r\n

@"+colList[i].txtColumn.Text+"

"+colList[i].cmbType.Text+createtype(colList[i].txtSize.Text)
+allownull(colList[i].cmbNull.Text)+",";
txtInsertQuery.Text += "\r\n
@"+colList[no-1].txtColumn.Text+"

"+colList[no-

1].cmbType.Text+createtype(colList[no-1].txtSize.Text)
+allownull(colList[no-1].cmbNull.Text);
}
else
{
txtInsertQuery.Text += "\r\n
@"+colList[0].txtColumn.Text+"
"+colList[0].cmbType.Text+createtype(colList[0].txtSize.Text)
+allownull(colList[0].cmbNull.Text);
}

txtInsertQuery.Text += "\r\n)";
txtInsertQuery.Text += "\r\nAS\r\nINSERT
INTO "+txtTableName.Text+"(";
if(no>1)
{
for(int i=0;i<no-1;i++)
txtInsertQuery.Text += colList[i].txtColumn.Text+",

";

txtInsertQuery.Text += colList[no1].txtColumn.Text+")";
}
else
{
txtInsertQuery.Text +=
colList[0].txtColumn.Text+")";
}
txtInsertQuery.Text += "\r\nVALUES(";
if(no>1)
{
for(int i=0;i<no-1;i++)
txtInsertQuery.Text += "@"+colList[i].txtColumn.Text+",

";

txtInsertQuery.Text +=
"@"+colList[no-1].txtColumn.Text+")";
}
else
{
txtInsertQuery.Text +=
"@"+colList[0].txtColumn.Text+")";
}
txtInsertQuery.Text += "\r\nGO";
if(checkforprimary())
{
int no_of_primkeys = 0;
for(int i=0; i<no; i++)

if(colList[i].chbPrimary.Checked) no_of_primkeys++;

if(no>no_of_primkeys)
{
txtUpdateQuery.Text = "CREATE
PROCEDURE dbo.sp_Update_"+txtTableName.Text;
txtUpdateQuery.Text +=
"\r\n(";
if(no>1)
{
for(int i=0;i<no-1;i++)
txtUpdateQuery.Text += "\r\n

@"+colList[i].txtColumn.Text+"

"+colList[i].cmbType.Text+createtype(colList[i].txtSize.Text)
+allownull(colList[i].cmbNull.Text)+",";
txtUpdateQuery.Text +=
"\r\n

@"+colList[no-1].txtColumn.Text+"

"+colList[no-

1].cmbType.Text+createtype(colList[no-1].txtSize.Text)
+allownull(colList[no-1].cmbNull.Text);
}
else
{
txtUpdateQuery.Text +=
"\r\n

@"+colList[0].txtColumn.Text+"

"+colList[0].cmbType.Text+createtype(colList[0].txtSize.Text)
+allownull(colList[0].cmbNull.Text);
}
txtUpdateQuery.Text +=
"\r\n)";
txtUpdateQuery.Text +=
"\r\nAS";
txtUpdateQuery.Text +=
"\r\nUPDATE "+txtTableName.Text;
txtUpdateQuery.Text +=
"\r\nSET ";
int no_of_noprimkeys = nono_of_primkeys;
for(int i=0;i<no;i++)
if(!
colList[i].chbPrimary.Checked)

{
no_of_noprimkeys--;

if(no_of_noprimkeys == 0) txtUpdateQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text;else
txtUpdateQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text+", ";
}
txtUpdateQuery.Text +=
"\r\nWHERE ";
int temp_no_of_primkeys =
no_of_primkeys;
for(int i=0;i<no;i++)

if(colList[i].chbPrimary.Checked)
{
temp_no_of_primkeys--;

if(temp_no_of_primkeys == 0) txtUpdateQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text;else
txtUpdateQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text+", ";
}
txtUpdateQuery.Text +=
"\r\nGO";
}
else
{
MessageBox.Show("Number of
primary key fields has to be less or equal to the total number of fields
for the UPDATE query to be
generated.","Warning",MessageBoxButtons.OK,MessageBoxIcon.Warning);
txtUpdateQuery.Text = "";
}

txtDeleteQuery.Text = "CREATE
PROCEDURE dbo.sp_Delete_"+txtTableName.Text;
txtDeleteQuery.Text += "\r\n(";
int tem_no_of_primkeys =
no_of_primkeys;
for(int i=0;i<no;i++)

if(colList[i].chbPrimary.Checked)
{
tem_no_of_primkeys--;
if(tem_no_of_primkeys ==
0) txtDeleteQuery.Text += "\r\n

@"+colList[i].txtColumn.Text+"

"+colList[i].cmbType.Text+createtype(colList[i].txtSize.Text)
+allownull(colList[i].cmbNull.Text);else txtDeleteQuery.Text +="\r\n
@"+ colList[i].txtColumn.Text+"
"+colList[i].cmbType.Text+createtype(colList[i].txtSize.Text)
+allownull(colList[i].cmbNull.Text)+",";
}
txtDeleteQuery.Text += "\r\n)";
txtDeleteQuery.Text += "\r\nAS";
txtDeleteQuery.Text += "\r\nDELETE
FROM "+txtTableName.Text;
txtDeleteQuery.Text += "\r\nWHERE ";
tem_no_of_primkeys = no_of_primkeys;
for(int i=0;i<no;i++)

if(colList[i].chbPrimary.Checked)
{
tem_no_of_primkeys--;
if(tem_no_of_primkeys ==
0) txtDeleteQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text;else
txtDeleteQuery.Text +=
colList[i].txtColumn.Text+"=@"+colList[i].txtColumn.Text+", ";
}
txtDeleteQuery.Text += "\r\nGO";

}
else
{
MessageBox.Show("There has to be at
least one field with primary key for the UPDATE and DELETE queries to be
generated.","Warning",MessageBoxButtons.OK,MessageBoxIcon.Warning);
txtUpdateQuery.Text = "";
txtDeleteQuery.Text = "";
}
}
else

MessageBox.Show("Please type positive

integer for number of columns and table

name.","Error",MessageBoxButtons.OK,MessageBoxIcon.Error);
} else
MessageBox.Show(checkvalidity(),"Error",MessageBoxButtons.OK,MessageBoxI
con.Error);
}
private void btnClose_Click(object sender, System.EventArgs
e)
{
Close();
}
private void btnCopyInsert_Click(object sender,
System.EventArgs e)
{
txtInsertQuery.SelectAll();
txtInsertQuery.Copy();
}
private void btnCopyUpdate_Click(object sender,
System.EventArgs e)
{
txtUpdateQuery.SelectAll();
txtUpdateQuery.Copy();
}

private void btnCopyDelete_Click(object sender,

System.EventArgs e)
{
txtDeleteQuery.SelectAll();
txtDeleteQuery.Copy();
}
private void frmMain_Load(object sender, EventArgs e)
{
}
}
}

CREATE DATABASE :
using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class CreateDB : System.Web.UI.Page

{
CommanClass objCls = new CommanClass();
ArrayList alDT = new ArrayList();
protected void Page_Load(object sender, EventArgs e)
{
}
protected void CreateDataBase(object sender, EventArgs e)
{
int flag = 0;
flag = objCls.CreateNewDataBase(txtDBN.Text);
// redirect to success page
if (flag > 0)
{
Response.Redirect("ErrorInfo.aspx");
}
else
{
//Response.Redirect("SuccessInfo.aspx?infotype=DB");
Response.Write("<script> alert('DataBase Successfull Created
!'); window.location='Home.aspx' </script>");
}
}
}

USER LOGIN :
using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class Login : System.Web.UI.Page

{
CommanClass objCS = new CommanClass();
// Local variables
bool IsValid = false;

protected void Page_Load(object sender, EventArgs e)

{
lblErrorInfo.Visible = false;
}
protected void btnSubmit_Click(object sender, EventArgs e)
{
IsValid = objCS.CheckLogin(txtUserName.Text, txtPassword.Text);
if (IsValid)
{
Response.Redirect("CreateDB.aspx");
}
else
{
lblErrorInfo.Visible = true;
}
}

User management:

using
using
using
using
using
using
using
using
using
using
using
using

System;
System.Collections;
System.Configuration;
System.Data;
System.Linq;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.HtmlControls;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Xml.Linq;

public partial class QueryMgt : System.Web.UI.Page

{
protected void Page_Load(object sender, EventArgs e)
{
}
public void GenerateSQL(object sender, EventArgs e)
{
//System.Diagnostics.Process.Start("E:\\Project_2011\\WebBased\\DataBase
Generator\\Generator\\QueryGenerator\\bin\\Debug\\QueryGenerator.exe");
System.Diagnostics.Process.Start(Server.MapPath("Generator\\QueryGenerat
or\\bin\\Debug\\QueryGenerator.exe"));
}
public void CreateUser(object sender, EventArgs e)
{
CommanClass cms = new CommanClass();
cms.CreateUserProfile(txtUser.Text, txtPwd.Text);
Response.Write("<script>alert('Profile created successfully');
window.location='Home.aspx';</script>");
}
}

CHAPTER-8
SYSTEM TESTING

System testing involves user training system testing and successful running of the
developed proposed system. The user tests the developed system and changes are made
according to their needs. The testing phase involves the testing of developed system using
various kinds of data.
An elaborate testing of data is prepared and the system is tested using the test
data. While testing, errors are noted and the corrections are made. The corrections are
also noted for the future use. The users are trained to operate the developed system.
TESTING:
System testing is the stage of implementation that is aimed at ensuring that the
system works accurately and efficiently before live operation commences. Testing is vital
to the success of the system. System testing makes logical assumption that if all the parts
of the system are correct, then the goal will be successfully achieved. A series of testing
are done for the proposed system before the system is ready for the user acceptance
testing.
The following are the types of Testing:
1. Unit Testing
2. Integration Testing

3. Validation Testing
4. Verification testing
5. User acceptance testing
8.1 Unit Testing
Unit testing focuses verification efforts on the smallest unit of the software
design, the module. This is also known as module testing. The modules are tested
separately. This testing was carried out during programming stage itself. In this testing
each module is found to be working satisfactorily as regards to the expected output from
the module.
8.2 Integration Testing
Data can be lost across an interface: one module can have adverse efforts on
another. Integration testing is the systematic testing for construction of program structure,
while at the same time conducting tests to uncover errors associated within the interface.

Here correction is difficult because the isolation of cause is complicated by the cast
expense of the entire program. Thus in the integration testing step, all the errors
uncovered are corrected for the next testing steps.
8.3 Validation Testing
At the conclusion of integration testing, software is completely assembled as a
package, interfacing errors have been uncovered and corrected and a final series of
software tests begins validation test has been conducted one of the two possible
conditions exists. One is the function or performance characteristics confirm to
specification and are accepted and the other is deviation from specification is uncovered
and a deficiency list is created.

8.4 Verification Testing

Verification is a fundamental concept in software design. This is the bridge between
customer requirements and an implementation that satisfies those requirements.
This is verifiable if it can be demonstrated that the testing will result in an
implementation that satisfies the customer requirements.
Inadequate testing or non-testing leads to errors that may appear few months later.
This will create two problems
Time delay between the cause and appearance of the problem.
The effect of the system errors on files and records within the system.
8.5 User Acceptance Testing
User acceptance testing of a system is the key factor of the success of any system.
The system under study is tested for the user acceptance by constantly keeping in touch
with the prospective system users at any time of developing and making changes
whenever required.

MAINTENANCE:
The objectives of this maintenance work are to make sure that the system gets
into work all time without any bug. Provision must be for environmental changes which
may affect the computer or software system. This is called the maintenance of the system.

Nowadays there is the rapid change in the software world. Due to this rapid change, the
system should be capable of adapting these changes. In our project the process can be
added without affecting other parts of the system.
Maintenance plays a vital role. The system liable to accept any modification after its
implementation. This system has been designed to favour all new changes. Doing this
will not affect the systems performance or its accuracy.
In the project system testing is made as follows:
The procedure level testing is made first. By giving improper inputs, the errors
occurred are noted and eliminated. Then the web form level testing is made. For example
storage of data to the table in the correct manner.
In the form, the zero length username and password are given and checked.
Also the duplicate username is given and checked. The client side validations are made.
The dates are entered in wrong manner and checked. Wrong email-id is given
and checked.
This is the final step in system life cycle. Here we implement the tested
error-free system into real-life environment and make necessary changes, which runs in
an online fashion. Here system maintenance is done every months or year based on
company policies, and is checked for errors like runtime errors, long run errors and other
maintenances like table verification and reports.
Implementation is the stage of the project when the theoretical design is
turned out into a working system. Thus it can be considered to be the most critical stage
in achieving a successful new system and in giving the user, confidence that the new
system will work and be effective.
The implementation stage involves careful planning, investigation of the
existing system and its constraints on implementation, designing of methods to achieve
changeover and evaluation of changeover methods.
Implementation is the process of converting a new system design into
operation. It is the phase that focuses on user training, site preparation and file conversion
for installing a candidate system. The important factor that should be considered here is
that the conversion should not disrupt the functioning of the organization.

The application is implemented in the Internet Information Services 5.0

web server under the Windows 2000 Professional and accessed from various clients.

SYSTEM IMPLEMENTATION
Implementation is the most crucial stage in achieving a successful
system and giving the users confidence that the new system is workable and effective.
Implementation of a modified application to replace an existing one. This type of
conversation is relatively easy to handle, provide there are no major changes in the
system.
Each program is tested individually at the time of development
using the data and has verified that this program linked together in the way specified in
the programs specification, the computer system and its environment is tested to the
satisfaction of the user. The system that has been developed is accepted and proved to be
satisfactory for the user. And so the system is going to be implemented very soon. A
simple operating procedure is included so that the user can understand the different
functions clearly and quickly.
Initially as a first step the executable form of the application is to be
created and loaded in the common server machine which is accessible to all the user and
the server is to be connected to a network. The final stage is to document the entire
system which provides components and the operating procedures of the system.

SCOPE FOR FUTURE DEVELOPMENT

Every application has its own merits and demerits. The project has covered
almost all the requirements. Further requirements and improvements can easily be done
since the coding is mainly structured or modular in nature. Changing the existing
modules or adding new modules can append improvements. Further enhancements can be
made to the application, so that the web site functions very attractive and useful manner
than the present one.

CHAPTER 9
PROBLEMS FASED
When there is a clear goal in sight but no clear set of directions or means to attain
that goal, then it is called a problem. problems can be broken down into four aspects;
goal, givens, means of transforming conditions, and obstacles.

Goal the goal is the desired end state which the problem solving is being
directed toward.
The hope is to reach that end state and be able to assess whether or not you
achieved what you wanted.
Givens- these are the objects , conditions ,and constraints that accompany a
problem ,and can be either explicit or implicit.
Means of transforming conditions- there should be a way of changing the initial
stateof the problem.this is most usually a persons knowledge or skill level. For
instance ,a computer programmer presented with a problem would utilize his or her
knowledge of programming language to transform the state of the problem.
Obstacles- the problem should present a challenge.if there are no challenges
involved and the situation can be easily solved then it is not so a problem so much as a
rountine task.
Every problem has a problem faced, which is the whole range of possible
states and operators.only some of these states and operators will bring the person closer
to the goal state. The problem starts at the initial state and operators are applied to
change the state, creating a series of intermediate states that should hopefully lead to the
final goal state

CHAPTER 10

FUTURE PLANS

Every application has its own merits and demerits. The project has
covered almost all the requirements. Further requirements and improvements can easily
be done since the coding is mainly structured or modular in nature. Changing the existing
modules or adding new modules can append improvements. Further enhancements can be
made to the application, so that the web site functions very attractive and useful manner
than the present one.

CONCLUSION
It is concluded that the application works well and satisfy the users. The
application is tested very well and errors are properly debugged. The site is

simultaneously accessed from more than one system. Simultaneous login from more than
one place is tested.
The application works according to the restrictions provided in their
respective System. Further enhancements can be made to the application, so that the
application functions very attractive and useful manner than the present one. The speed of
the transactions become more enough now.

APPENDIX

BIBLIOGRAPHY

1.STEVE HARRIS AND ROBMACDONALD,

WEB DEVELOPMENT WITH VB.NET
-APRES
2. MATTHEW MACDONALD ,
MICROSOFT VISUAL BASIC.NET PROGRAMMERS COOKBOOK
-TATA McGRAW HILL EDITION
3. CHRIS GOODE, JOHN KAUFFMAN
BEGINNING ASP.NET 1.0 WITH VISUAL BASIC.NET
-WROX PROGRAMMER TO PROGRAMMER
4. Douglas O.Reilly ,
DESIGNING MICROSOFT ASP.NET APPLICATIONS
-TATA McGRAW HILL EDITION