Blood Donor's Management System

Blood Donors Management System
INTRODUCTION:
The project entitled BLOOD DONORS MANAGEMENT is a pilot project
for new Blood donor to be start soon in the College. The management planned
this blood donor to operate on the next month. They have a big plan to collect the
blood Group from many different students. To manage all these they require fullfledged software, which will take care all these.
PROJECT:
BLOOD DONOR MANAGEMENT is a software site to maintain day-to-day
transactions in blood donors. This software help to register all the donors, Blood
collection details, blood issued details etc.,
OBJECTIVE:
The main objective of this site is to automate the complete operations of the
blood donor. They need maintain hundreds of thousands of records. Also
searching should be very faster so they can find required details instantly.
MAIN MODULES OF THE PROJECT:
This project has the following modules, to manage all the requirements
of the blood donor.
1. Blood Bank details
2. College Students Details
3. Donor Details
4. Blood collection details
5. Blood Issued Details
6. Reports
MODULE DESCRIPTION:
BLOOD BANK DETAILS:
This module allow the administrator to maintain the blood bank details with
corresponding address, and necessary contact details.
COLLEGE STUDENT DETAILS:
The college student details allow the students to register their identity into the site
with proper proofs.
DONOR DETAILS:
The donor details allow the donor to enter their identities with respective address
and associative contact details.
BLOOD COLLECTION DETAILS:
The blood collection details module allow the donor to maintain their blood
related details into the site for the requestors.
BLOOD ISSUED DETAILS:
The blood issued details module allows the donor who are all issued their blood to
the respective requestors.
REPORTS:
The reporting module allows the user as well as administrator to maintain the
records in a report wise for printing state manner.
PLATFORM:
SOFTWARE REQUIREMENTS:
Operating system
Windows XP.
Coding Language
ASP.NET
Data Base
MS-Access
HARDWARE REQUIREMENTS:
System
Pentium IV 2.4 GHz.
Hard Disk
40 GB.
Floppy Drive :
1.44 Mb.
Monitor
15 VGA Colour.
Mouse
Logitech.
Ram
512 Mb.
DATABASE STRUCTURE:
REGISTER:
Batch Master:
BLOOD GROUP MASTER:
DEPARTMENT MASTER:
FEEDBACK:
SCREENS & CODINGS:
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;
using System.Data.OleDb;
using System.Windows.Forms;
public partial class Register : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
e)
protected void Page_Load(object sender, EventArgs

{
Cn = new
OleDbConnection(ConfigurationManager.ConnectionStrings[
"Con"].ConnectionString);
Cn.Open();
if (Page.IsPostBack == false)
{
string S;
S = "Select * From DeptMstr";
Cmd = new OleDbCommand(S, Cn);
dr = Cmd.ExecuteReader();
DrpDept.Items.Add("----------------------------------Select------------------------------");
while (dr.Read())
{
DrpDept.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
string S1;
S1 = "Select * From BldGrp";
Cmd = new OleDbCommand(S1, Cn);
DrpBldGrp.Items.Add("----------------------------------Select------------------------------");
while (dr.Read())
{
DrpBldGrp.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
string S2;
S2 = "Select * From Batch";

Cmd = new OleDbCommand(S2, Cn);
DrpBatch.Items.Add("----------------------------------Select------------------------------");
while (dr.Read())
{
DrpBatch.Items.Add(dr.GetString(1).ToString());
}
Cmd.Dispose();
dr.Close();
DrpDegree.Items.Add("----------------------------------Select------------------------------");
DrpDegree.Items.Add("UG");
DrpDegree.Items.Add("PG");
DrpGender.Items.Add("----------------------------------Select------------------------------");
DrpGender.Items.Add("MALE");
DrpGender.Items.Add("FEMALE");
DrpWillToDon.Items.Add("----------------------------------Select------------------------------");
DrpWillToDon.Items.Add("YES");
DrpWillToDon.Items.Add("NO");
}
}
protected void ImageButton2_Click(object sender,
ImageClickEventArgs e)
{
Clear();
}
public void Clear()
{
TxtRNO.Text = "";
TxtName.Text = "";
DrpBldGrp.Text =
"----------------------------------Select------------------------------";
DrpDept.Text =
"----------------------------------Select------------------------------";
DrpBatch.Text =
"----------------------------------Select------------------------------";
DrpDegree.Text =
"----------------------------------Select------------------------------";
DrpWillToDon.Text =
"----------------------------------Select------------------------------";
DrpGender.Text =
"----------------------------------Select------------------------------";
TxtSec.Text = "";
TxtDOB.Text = "";
TxtContact.Text = "";
TxtMail.Text = "";
TxtAddr.Text = "";
TxtWeight.Text = "";
TxtUN.Text = "";
TxtPwd.Text = "";
}
{
string str = "";
if (TxtRNO.Text == "")
{
str += "Enter The Register Number\n";
}
if (DrpGender.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The Gender\n";
}
if (DrpDegree.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The Degree\n";
}
if (DrpDept.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The Department\n";
}
if (DrpBatch.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The Batch\n";
}
if (DrpBldGrp.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The Blood Group\n";
}
if (DrpWillToDon.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The User Willingness\n";
}
if (DrpWillToDon.Text ==
"----------------------------------Select------------------------------")
{
str += "Select The User Willingness\n";
}
if (TxtName.Text == "")
{
str += "Enter The Name\n";
}
if (TxtSec.Text == "")
{
str += "Enter The Section\n";
}
if (TxtDOB.Text == "")
{
str += "Enter The Date Of Birth\n";
}
if (TxtContact.Text == "")
{
str += "Enter The Contact Number\n";
}
if (TxtMail.Text == "")
{
str += "Enter The Mail-ID\n";
}
if (TxtAddr.Text == "")
{
str += "Enter The Address\n";
}
if (TxtWeight.Text == "")
{
str += "Enter The Weight\n";
}
if (TxtUN.Text == "")
{
str += "Enter The User Name\n";
}
if (TxtPwd.Text == "")
{
str += "Enter The Password\n";
}
if (str == "")
{
string S;
S = "Insert Into Register Values(" +
TxtRNO.Text + ",'" + TxtName.Text + "','" + TxtUN.Text
+ "','" + TxtPwd.Text + "','" + DrpBldGrp.Text + "','"
+ DrpDept.Text + "','" + DrpDegree.Text + "','" +
DrpBatch.Text + "','" + TxtSec.Text + "','" +
DrpGender.Text + "','" + TxtDOB.Text + "','" +
TxtContact.Text + "','" + TxtMail.Text + "','" +
TxtAddr.Text + "','" + DrpWillToDon.Text + "','" +
TxtWeight.Text + "')";
Cmd.ExecuteNonQuery();
Cmd.Dispose();
MessageBox.Show("Successfully Registered
Your Identity", "Blood Donor's System :");
Clear();
}
else
{
MessageBox.Show(str, "Blood Donor's
System :");
}
}
}
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
using
using
using
using
System.Xml.Linq;
public partial class Login : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
e)
Cn = new
Cn.Open();
}
{
if (TxtUN.Text == "Admin" && TxtPwd.Text ==
"Admin")
{
Response.Redirect("DeptMstr.aspx");
}
else
{
String S;
S = "Select * From Register Where UN='" +
TxtUN.Text + "' And Pwd='" + TxtPwd.Text + "'";
if (dr.Read())
{
Response.Redirect("UserPage.aspx");
}
else
{
MessageBox.Show("Invalid
Authentication", "Blood Donor's System :");
}
dr.Close();
Cmd.Dispose();
}
}
{
TxtUN.Text = "";
TxtPwd.Text = "";
}
}
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
using
using
using
using
using
using
System.Web.UI;
System.Xml.Linq;
public partial class Feedback : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
e)
Cn = new
Cn.Open();
}
{
string Str = "";
if (TxtName.Text == "")
{
Str += "Enter The Name\n";
}
if (TxtMail.Text == "")
{
Str += "Enter The Mail-ID\n";
}
if (TxtCN.Text == "")
{
Str += "Enter The Contact Number\n";
}
if (TxtComments.Text == "")
{
Str += "Enter The Comments\n";
}
if (Str == "")
{
string S;
S = "Insert Into Feedback Values('" +
TxtName.Text + "','" + TxtCN.Text + "','" +
TxtMail.Text + "','" + TxtComments.Text + "')";
Cmd.Dispose();
MessageBox.Show("Successfully Posted Your
Comments", "Blood Donor's System :");
Clear();
}
else
{
MessageBox.Show(Str, "Blood Donor's
System :");
}
}
{
Clear();
}
public void Clear()
{
TxtName.Text = "";
TxtMail.Text = "";
TxtComments.Text = "";
TxtCN.Text = "";
}
}
using
using
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
System.Xml.Linq;
System.Data.OleDb;
System.Windows.Forms;
public partial class SearchDonars : System.Web.UI.Page

{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;

e)
Cn = new
Cn.Open();
{
string S;
S = "Select * From Register";
DrpBldGrp.Items.Add("----------------------------------Select------------------------------");
while (dr.Read())
{
DrpBldGrp.Items.Add(dr.GetString(4).ToString());
}
Cmd.Dispose();
dr.Close();
}
}
protected void
DrpBldGrp_SelectedIndexChanged(object sender, EventArgs
e)
{
if (DrpBldGrp.Text !=
"----------------------------------Select------------------------------")
{
LstSrch.Items.Clear();
string S;
S = "Select * From Register";
while (dr.Read())
{
LstSrch.Items.Add(dr.GetValue(0).ToString());
}
dr.Close();
Cmd.Dispose();
}
}
protected void LstSrch_SelectedIndexChanged(object
sender, EventArgs e)
{
string S;
S = "Select * From Register Where RNO=" +
LstSrch.SelectedItem.Value.ToString() + "";
if(dr.Read())
{
LblDisp.Text +="NAME : "+
dr.GetString(1).ToString()+"<br>";
LblDisp.Text += "CONTACT NUMBER : " +
dr.GetString(11).ToString() + "<br>";
LblDisp.Text += "E-MAIL-ID : " +
LblDisp.Text += "DEGREE : " +
LblDisp.Text += "DEPARTMENT : " +
LblDisp.Text += "BATCH : " +
LblDisp.Text += "SECTION : " +
LblDisp.Text += "ADDRESS : " +
}
dr.Close();
Cmd.Dispose();
}
{
LstSrch.Items.Clear();
DrpBldGrp.Text =
"----------------------------------Select------------------------------";
LblDisp.Text = "";
}
}
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
System.Xml.Linq;
public partial class DeptMstr : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
int a;
e)

{
Cn = new
Cn.Open();
{
Disp();
}
}
public void Disp()
{
string S;
S = "Select MAX(DID) From DeptMstr";
if (dr.Read())
{
a = Convert.ToInt32(dr.GetValue(0)) + 1;
TxtDID.Text = a.ToString();
}
dr.Close();
Cmd.Dispose();
}
{
if (TxtName.Text != "")
{
string S;
S = "Insert Into DeptMstr Values(" +
TxtDID.Text + ",'" + TxtName.Text + "')";
Cmd.Dispose();
MessageBox.Show("Successfully Saved",
"Blood Donor's System :");
TxtName.Text = "";
Disp();
}
else
{
MessageBox.Show("Enter The Department
Name", "Blood Donor's System :");
}
}
{
TxtName.Text = "";
Disp();
}
{
if (TxtDID.Text != "")
{
String S;
S = "Select * From DeptMstr Where DID=" +
TxtDID.Text + "";
if (dr.Read())
{
TxtName.Text =
dr.GetString(1).ToString();
}
dr.Close();
Cmd.Dispose();
}
}
{
{
string S;
S = "Update DeptMstr Set DName='" +

TxtName.Text + "' Where DID=" + TxtDID.Text + "";
Cmd.Dispose();
MessageBox.Show("Successfully Edited",
TxtName.Text = "";
Disp();
}
else
{
}
}
{
{
string S;
S = "Delete From DeptMstr Where DID=" +
TxtDID.Text + "";
Cmd.Dispose();
MessageBox.Show("Successfully Deleted",
TxtName.Text = "";
Disp();
}
else
{
}
}
}
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
System.Xml.Linq;
public partial class BloodGroupMstr :
System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
int a;
e)
Cn = new
Cn.Open();
{
Disp();
}
}
public void Disp()
{
string S;
S = "Select MAX(BID) From BldGrp";
if (dr.Read())
{
TxtBGID.Text = a.ToString();
}
dr.Close();
Cmd.Dispose();
}
{
{
string S;
S = "Insert Into BldGrp Values(" +
TxtBGID.Text + ",'" + TxtName.Text + "')";
Cmd.Dispose();
TxtName.Text = "";
Disp();
}
else
{
MessageBox.Show("Enter The Blood Group
}
}
{
TxtName.Text = "";
Disp();
}
}
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
System.Xml.Linq;
public partial class BatchMstr : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbCommand Cmd;
OleDbDataReader dr;
int a;
e)
Cn = new
Cn.Open();
{
Disp();
}
public void Disp()

{
string S;
S = "Select MAX(BID) From Batch";

if (dr.Read())
{
TxtBID.Text = a.ToString();
}
dr.Close();
Cmd.Dispose();
}
{
if (TxtBatch.Text != "")
{
string S;
S = "Insert Into Batch Values(" +
TxtBID.Text + ",'" + TxtBatch.Text + "')";
Cmd.Dispose();
TxtBatch.Text = "";
Disp();
}
else
{
MessageBox.Show("Enter The Batch Name",
}
}
{
TxtBatch.Text = "";
Disp();
}
}
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Collections;
System.Data;
System.Linq;
System.Web;
System.Web.UI;
System.Xml.Linq;
public partial class FeedbackView : System.Web.UI.Page
{
OleDbConnection Cn;
OleDbDataAdapter da;
DataSet ds;

e)
Cn = new
Cn.Open();
string S;
S = "Select Name as NAME,Mail as MailID,Contact
as CONTACT,Comment as COMMENTS From Feedback";
da = new OleDbDataAdapter(S,Cn);
ds = new DataSet();
da.Fill(ds, "SS");
GridView1.DataSource = ds.Tables["SS"];
GridView1.DataBind();
}
}
SOFTWARE DESCRIPTION
About ASP.Net
ASP.NET is more than 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
with ASP, it also provides a new programming model and infrastructure for more secure,
scalable and stable applications. You can feel free to augment your existing ASP
applications by incrementally adding ASP.NET functionality to them.
ASP.NET is a compiled, NET-based environment; you 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, 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.
ASP.NET Technology Backgrounder

ASP.NET, in turn, is built on the .NET Framework, so the entire framework is
available to any ASP.NET application. Your applications can be authored in any language
compatible with the common language runtime, including Microsoft Visual Basic, Visual
C#, and JScript .NET. The following sections provide an overview of the features offered
by ASP.NET.
ASP.NET Page Framework and the Web Forms Page

The ASP.NET page framework is a programming framework that
runs on a Web server to dynamically produce and manage Web Forms
pages. In Visual Studio, Web Forms provides a forms designer, editor,
controls, and debugging, which together allow you to rapidly build
server-based, programmable user interfaces for browsers and Web
client devices.
Web Forms pages run on any browser or client device. However,
you can design your Web Forms page to target a specific browser, such
as Microsoft Internet Explorer 5, and take advantage of the features
of a specific browser or client device. ASP.NET supports mobile controls
for Web-enabled devices such as cellular phones, handheld computers
and personal digital assistants (PDAs).
The ASP.NET page framework creates an abstraction of the traditional clientserver Web interaction so that you can program your application using traditional
methods and tools that support rapid application development (RAD) and object-oriented
programming (OOP). Within Web Forms pages you can work with HTML elements using
properties, methods, and events. The ASP.NET page framework removes the
implementation details of the separation of client and server inherent in Web-based
applications by presenting a unified model for responding to client events in code that
runs at the server. The framework also automatically maintains the state of a page and the
controls on that page during the page processing life cycle.
The ASP.NET page framework and Web Forms pages also support server controls
that encapsulate common UI functionality in easy-to-use, reusable controls..
XML Web Services

ASP.NET supports XML Web services. An XML Web service is a component
containing business functionality exposed through Internet protocols. An XML Web
service enables applications to exchange information between Web-based applications
using standards like HTTP and XML messaging to move data across firewalls. XML Web
services are not tied to a particular component technology or object-calling convention.
As a result, programs written in any language, using any component model, and running
on any operating system can access XML Web services.
State Management Facilities

ASP.NET provides intrinsic state management functionality that
allows you to save and manage application-specific, session-specific,
and
developer-defined
information.
This
information
can
be
independent of any controls on the page. It can be shared between

pages, such as customer information or the contents of a shopping
cart.
ASP.NET offers distributed state facilities. You can create multiple instances of the same
application on one computer or on several computers.
Application Events
ASP.NET allows you to include application-level event-handling
code in the optional Global.aspx file. You can use application events to
manage application-wide information and perform orderly application
startup and cleanup tasks. For more information, see The Global.aspx
File.
Compilation
All ASP.NET code, including server scripts, is compiled, which
allows for strong typing, performance optimizations and early binding,
among other benefits. Once the code has been compiled, the runtime
further
compiles
ASP.NET
to
native
code,
providing
improved
performance.
Configuration
ASP.NET configuration settings are stored in XML-based files. Since
these XML files are ASCII text files, you can read and modify them, so
it is simple to make configuration changes to your Web applications.
Each of your applications can have its own configuration file and you
can extend the configuration scheme to suit your requirements. For
more information, see Configuration Files.
Deployment
Visual Studio provides a simplified mechanism for deploying
applications to local or remote servers. You can install files by simply
copying them to your specified application directories, or by using a
more specialized and configurable deployment project.
Security
ASP.NET
provides
default
authorization
and
authentication
schemes for Web applications. You can easily remove, add to or

replace these schemes depending upon the needs of your application.
Debugging Support
ASP.NET takes advantage of the runtime-debugging infrastructure to provide
cross-language and cross-computer debugging support used both locally and remotely
from a Web server. In addition, the ASP.NET page framework provides a trace mode that
enables you to insert instrumentation messages into your forms. For more information,
see Debugging Managed Code.
You can debug both managed and unmanaged objects, as well as all
languages supported by the common language runtime and script
languages. For more information, see Debugging Script and Web
Applications.
Optimization
ASP.NET incorporates a variety of features and tools that allow
you to design and implement high-performance Web applications.
These features include:
A process model that is improved over ASP.
Compiling requested pages and storing them on the server

automatically.
ASP.NET-specific performance counters.
Web application testing tools.
ASP.NET gives you the ability to create Web applications that meet the
demands created when the application processes a large amount of
requests simultaneously. For details, see ASP.NET Optimization.
Performance Counter Support

A performance counter is the mechanism by which Windows
collects performance data on various system resources. ASP.NET
supports two groups of performance counters accessible to your
applications:
ASP.NET System performance counter group.
ASP.NET Application performance counter group.
The ASP.NET system group is accessible through the Performance Monitor

Application (PerfMon.exe) under the ASP.NET System performance counter object,
while the ASP.NET application group is accessible via the ASP.NET Application
performance counter object. ASP.NET also supports the creation of custom performance
counters.
Integrating with IIS

This release of ASP.NET uses IIS 5.0 as the priKim host environment. When
considering ASP.NET authentication, you should understand the interaction with IIS
authentication services.
IIS always assumes that a set of credentials maps to a Windows NT account and
uses them to authenticate a user. There are three different kinds of authentication
available in IIS 5.0: basic, digest, and Integrated Windows Authentication (NTLM or
Kerberos). You can select the type of authentication to use in the IIS administrative
services. For more information on IIS authentication, see the IIS documentation.
If you request a URL containing an ASP.NET application, the request and
authentication information are handed off to the application. ASP.NET provides the two
additional types of authentication described in the following table.
ASP.NET authentication provider

Forms authentication
Description
A system by which unauthenticated
requests are redirected to an HTML
form
using
redirection.
HTTP
The
client-side
user
provides
credentials and submits the form. If

the
application
authenticates
the
request, the system issues a form that

contains the credentials or a key for
reacquiring the identity. Subsequent
requests are issued with the form in
the
request
headers;
they
are
authenticated and authorized by an

ASP.NET handler using whatever
validation
Passport authentication
method
the
application
developer specifies.
Centralized authentication
service
provided by Microsoft that offers a

single log on and core profile services
for member sites.
USING ASP.NET CONFIGURATION FILES

ASP.NET configuration, of which security is a part, has a hierarchical architecture.
All configuration information for ASP.NET is contained in files named Web.config and
Machine.config. Web.config can be placed in the same directories as the application files.
The Machine.config file is in the Config directory of the install root. Subdirectories
inherit a directory's settings unless overridden by a Web.config file in the subdirectory. In
a Web.config file, there are sections for each major category of ASP.NET functionality.
To see an example of the way in which the hierarchical configuration system works for
security see Hierarchical Configuration Architecture
There are three major subsections: authentication, authorization and identity. The
values for each of the elements are usually set by overriding this section of the computerlevel configuration file with a similar section in an application configuration file placed
in the application root. All subdirectories automatically inherit those settings. However,
subdirectories can have their own configuration files that override other settings.
ASP.NET Data Access

The .NET Framework includes a new data access technology
named ADO.NET, an evolutionary improvement to ADO. However, the
classes that make up ADO.NET are different from the ADO objects that
you might be familiar with. Some changes must be made to existing
ADO applications to convert them to ADO.NET. The changes do not
have to be made to existing ADO applications immediately for them to
run under ASP.NET, however, as ADO will function under ASP.NET.
Nonetheless, converting ADO applications to ADO.NET is worthwhile.
For
disconnected
applications,
ADO.NET
offers
performance
advantages over ADO disconnected record sets. Whereas ADO requires

that transmitting and receiving components be COM objects, ADO.NET
transmits data in standard XML format so that COM marshaling or
data-type conversions are not required.
Data retrieved from a database is generally used in one of two ways. The records
may be examined and manipulated by ASP code as a precursor to some other action,
without being displayed directly to the client, or the records simply may be displayed to
the client in a table or grid. The examples in this topic show how to convert a typical
ADO scenario to ADO.NET. There is a great deal more to the ADO.NET model than
these short examples illustrate; this is simply a quick overview of how to port common
ASP and ADO scenarios to the .NET Framework.
Working with a Single Table

The first block of code in the following example is typical of an ASP application
that uses ADO to read and manipulate a set of records returned from a single SQL query.
It uses an ADO Recordset object to read the data records returned from the Northwind
sample database supplied with Microsoft Access. This code would be contained in a file
with an .asp file name extension.
ADO.NET DataSet object, which in this case contains one data table that is used
in much the same way as an ADO Recordset. Note that a DataSet can consist of
collections of one or more DataTables, DataRelations, and Constraints that form a
memory-resident database, so an ADO.NET DataSet is a great deal more flexible than an
ADO Recordset.
In order to use ADO.NET, you need to import the System.Data
and System.Data.OleDb namespaces. If your data source is a SQL
Server database, import the System.Data.SqlClient namespace instead
of System.Data.OleDb. For details on using the connection objects for
ADO and SQL .NET Data Providers, see Managed Connections.
In cases where a database query (even a multi-table join query), returns a single
set of records, you can use a single DataTable (MyTable in the example) in much the
same way that you use an ADO Recordset.
Working with Multiple Database Tables

The ADO.NET DataSet can contain multiple tables and a set of relations that
describes a local copy of a relational database. Think of it as a mini-database in server
memory. Using the relation objects, your code can navigate through the collection of
tables to access data records in complex ways without making further queries to the main
data store. For more information about the components of a Dataset.
Displaying Data in a Control
To display database data in tabular format in a browser, ASP developers have had to
write code to intersperse the data with HTML tags to build HTML tables on the fly.
ASP.NET includes DataGrid, DataList, and Repeater server controls that greatly
simplify the task of displaying tabular data on a Web page. ADO.NET datasets can be
easily bound to these controls; the ASP.NET engine, working with a control, sends pure
HTML 3.2 to the browser, producing richly formatted layouts to the user.
ASP.NET Web Application Security

Most Web sites need to selectively restrict access to some portions of the site. You
can think of a Web site as somewhat analogous to an art gallery. The gallery is open for
the public to come in and browse, but there are certain parts of the facility, such as the
business offices, that are restricted to people with certain credentials, such as employees.
When a Web site records users' must be secured from public access. ASP.NET security
features address these and many credit card information, for example, the file or database
that stores such information other security issues.
ASP.NET, in conjunction with Internet Information Services (IIS),
can authenticate user credentials such as names and passwords, using
any of the following authentication methods:
Windows: Basic, digest, or Integrated Windows Authentication
Microsoft Passport Authentication
Forms
Client Certificates
ASP.NET controls access to site information by comparing authenticated

credentials, or representations of them, to NTFS file system permissions or to an XML
file that lists authorized users, authorized roles (groups), or authorized HTTP verbs.
ASP.NET Optimization
up ADO.NET are different from the ADO objects that you might be familiar with.
Some changes must be made to existing ADO applications to convert them to ADO.NET.
In this day of business-to-business and business-to-consumer e-commerce, slow Web
applications can waste resources and drive customers away from your company. Web site
performance is an extremely important issue for the developer writing code and for the
system administrator maintaining applications.
Fortunately, ASP.NET incorporates a variety of features and tools that allow you
to design and implement high-performance Web applications. These features include the
following:
An improved process model
Compilation of requested pages and automatic storage on the server
ASP.NET-specific performance counters
Web application testing tools
ASP.NET gives you the ability to create Web applications that meet the demands
that arise when they must process large numbers of requests simultaneously
ASP.NET Data Access

ADO The .NET Framework includes a new data access technology named
ADO.NET, an evolutionary improvement to ADO. However, the classes that make
The changes do not have to be made to existing ADO applications immediately for
them to run under ASP.NET, however, as ADO will function under ASP.NET.
Nonetheless, converting ADO applications to ADO.NET is worthwhile. For disconnected
applications, ADO.NET offers performance advantages over ADO disconnected record
sets. Whereas ADO requires that transmitting and receiving components be COM objects,
ADO.NET transmits data in standard XML format so that COM marshaling or data-type
conversions are not required.
Data retrieved from a database is generally used in one of two ways. The records
may be examined and manipulated by ASP code as a precursor to some other action,
without being displayed directly to the client, or the records simply may be displayed to
the client in a table or grid. The examples in this topic show how to convert a typical
ADO scenario to ASP.NET. There is a great deal more to the ADO.NET model than these
short examples illustrate; this is simply a quick overview of how to port common ASP
and ADO scenarios to the .NET Framework.
Working with a Single Table

The first block of code in the following example is typical of an ASP application
that uses ADO to read and manipulate a set of records returned from a single SQL query.
It uses an ADO Recordset object to read the data records returned from the Northwind
sample database supplied with Microsoft Access. This code would be contained in a file
with an .asp file name extension.
ADO.NET DataSet object, which in this case contains one data table that is used in
much the same way as an ADO Recordset. Note that a DataSet can consist of collections
of one or more DataTables, DataRelations, and Constraints that form a memory-resident
database, so an ADO.NET DataSet is a great deal more flexible than an ADO Recordset.
In order to use ADO.NET, you need to import the System.Data and
System.Data.OleDb namespaces. If your data source is a SQL Server database, import
the System.Data.SqlClient namespace instead of System.Data.OleDb. For details on
using the connection objects for ADO and SQL .NET Data Providers, see Managed
Connections.
In cases where a database query (even a multi-table join query), returns a single set
of records, you can use a single DataTable (MyTable in the example) in much the same
way that you use an ADO Recordset.
Working with Multiple Database Tables

The ADO.NET DataSet can contain multiple tables and a set of relations that
describes a local copy of a relational database. Think of it as a mini-database in server
memory. Using the relation objects, your code can navigate through the collection of
tables to access data records in complex ways without making further queries to the main
data store. For more information about the components of a Datasets.
Displaying Data in a Control

To display database data in tabular format in a browser, ASP developers have had to
write code to intersperse the data with HTML tags to build HTML tables on the fly.
ASP.NET includes DataGrid, DataList, and Repeater server controls that greatly
simplify the task of displaying tabular data on a Web page. ADO.NET datasets can be
easily bound to these controls; the ASP.NET engine, working with a control, sends pure
HTML 3.2 to the browser, producing richly formatted layouts to the user.
ASP.NET Web Application Security

Most Web sites need to selectively restrict access to some portions of the site. You
can think of a Web site as somewhat analogous to an art gallery. The gallery is open for
the public to come in and browse, but there are certain parts of the facility, such as the
business offices, that are restricted to people with certain credentials, such as employees.
When a Web site records users' must be secured from public access. ASP.NET security
features address these and many credit card information, for example, the file or database
that stores such information other security issues.
ASP.NET, in conjunction with Internet Information Services (IIS), can authenticate user
credentials such as names and passwords, using any of the following authentication
methods:
Windows: Basic, digest, or Integrated Windows Authentication

(NTLM or Kerberos).
Microsoft Passport Authentication
Forms
Client Certificates
ASP.NET controls access to site information by comparing authenticated credentials, or

representations of them, to NTFS file system permissions or to an XML file that lists
authorized users, authorized roles (groups), or authorized HTTP verbs.
ASP.NET Optimization
In this day of business-to-business and business-to-consumer e-commerce, slow
Web applications can waste resources and drive customers away from your company.
Web site performance is an extremely important issue for the developer writing code and
for the system administrator maintaining applications.
Fortunately, ASP.NET incorporates a variety of features and tools that allow you to
design and implement high-performance Web applications. These features include the
following:
An improved process model
Compilation of requested pages and automatic storage on the

server
ASP.NET-specific performance counters
Web application testing tools
ASP.NET gives you the ability to create Web applications that meet the demands that
arise when they must process large numbers of requests simultaneously
MS-ACCESS
Access offers a variety of features for different database needs. It can be used to
develop five general types of applications:
Personal applications
Applications used to run a small business
Department applications
Corporations- wide applications
Front-end for enterprise-wide client/server applications
Backend tables can be linked to the front-end applications. The process of linking
to backend tables is almost identical to that of linking to tables in other access databases.
After the back end tables have been linked to the front-end applications, they can be
treated like any other linked tables. Access utilizes ODBC to communicate with the back
end tables. Our application sends an Access SQL statement to the Access Jet Engine.
Jet translates the Access SQL statement into ODBC SQL. The ODBC SQL
statement is then sent to the ODBC Manager. The ODBC manger locates the correct
ODBC driver and passes it the ODBC SQL statement. The ODBC driver, supplied by the
back end vendor, translates the ODBC SQL statement into the back-ends specific dialect.
The back end specific is sent to the SQL server and to the appropriate database.
Data Base
A database is an organized list of data that can be queried to find information
quickly and easily based and chosen reference point, such as a last name or security
number. In database terminology, the columns are called fields and the rows are called
records. This kind organization in a database is called a data table, or just a table.
Access
Access is a RDBMS that you can store and manipulate large amount of
information. A relational database is a database, which consist of tables of related
information that are linked together based on key field. <S Access supports GUI features
and entire programming language, VBA (Visual Basic or Application) that can be used to
develop richer and more developed application. MS Access database can act as a backend
database for VB. While using VB as a front-end tool, MS Access supports the user with
its powerful DBMS functions.
Main Elements of Access

ACCESS is an object-oriented program. Objects are modules, which provide
information and program, which the user can directly apply to create application.
Access has the following windows
1. Data base Windows
2. Tables
3. Queries
4. Forms
5. Reports
6. Macros
7. Modules
8. Relationship
Database Windows
In Access all, objects a dataase are stored in a single file and the file name has an
MDB extension.
Tables
Tables are the primary building block of ACCESS database. All datas are stored
in tables.
Queries
A query is a question that you ask of the data that I stored in the tables of your
database
New Features in MS Access

MS Accesss offers many new and improved features to help create powerful
databse applications.
New objects, properties , methods and others language elements
Accessing the Internet or an intranet from your applicaions
Creating custom objects with class modules.
Cjstomizing menus and tool bars in your applications
Removing source code from uyour applications.
Working with version 3.5 of the micro-soft ject database engine.
Replicating only a specified part of a database.
Using new featurs in the module window
Using the object browser as a reference for objects and their numbers
5.5 TESTING
Software testing is a critical element of software quality
assurance and represents the ultimate view of specification, design
and coding. The increasing visibility of software as a system element
and attendant cost associated with a software failure is the motivating
forces for well planned through testing. The programmer creates a
series of test cases that are intended to demolish the software
engineering process that could be reviewed as a preconceived notion
of the correctness of the software just developed and overcome a
conflict of interest that occurs when errors are uncovered. Testing is a
process of executing a program with the intent of finding another error.
If the test is conducted successfully it will automatically uncover errors
in the software.
Testing Principles:
o All the test should be traceable to assessed requirements.
o Test should be planned long by testing begins.
o Testing should begin in the small and progress toward testing in the large.
Black Box Testing:

In this testing inputs are given to the system and outputs are tested. There is no
necessary for watching the internal variables in the system and what are the changes
made on them for the required output. Giving input and testing output, as said above,
implement testing the system.
White Box Testing
It is just the vice versa of the black box testing. Here watching the internal
variables during testing are not needed. This gives a clear idea what is going on during
execution of the system. This points out where the bugs occurred and we remove it.
System Testing
System testing is design to uncover weakness that was not found in earlier tests.
This includes forced system failure and validation of the total system, as its users in the
operational environment will implement it. The total system is also testing or recovery
and fallback after various major failures to ensure that no data are lost during emergency.
It is concerned with interface, decision logic, and control flow recovery procedures,
throughput capacity and timing characteristics of the output system.
Regression Testing
Regression testing involves executing old test cases to test that no new errors have
been introduced. This testing is performed when some changes are made to an existing
system. The modified system needs to be tested to make sure that the new features to be
added to indeed work. However, as modification have been made to an existing system,
testing also has to be done to make sure that the modification has not had any undesired
side effect of making some of the earlier services faulty. This is the task of regression
testing.
Device Testing
The software testing process commences once the program is created and the
documentation and related data structures are design. Software testing is essential for
correcting errors. Otherwise the program or the project is not said to complete.
The following are the types of testing:
1. Unit testing
2. Integration testing
Unit Testing
Unit testing focuses verification effort on the smallest unit of software design
(i.e.) the module. Units Testing exercises specific paths in a modules control structure to
ensure complete coverage and maximum error detection. This test focuses on each
module individually; ensure that it function property as a unit. Hence, the name is unit
testing.
Validation Testing
If the user enters invalid data type, it will show the error message. For example, in
this module the user type the employee number as character it indicates the error to
validate data.
Integration Testing
Integration testing
addresses
the issues associated with the
dual problems of verification and program construction. After the

software has been integrated a set of High order tests are conducted
.the main objectives in this testing process are to take unit-tested
modules and build a program structure has been dictated by design.
CONCLUSION:
This project Blood Donor System handling and managing the donor database in
an efficient manner. This system is more innovative to use, any user can make up an
easier and faster transactions between users. This site can be used under any private
concern, for flexibly handling the databases, to get dispatches the data to process them for
individual usages. Thus it makes the system more flexible, and more reliable for use.
For all the above this site is the perfect place for the users especially students who
preferred to save the time, and entered into the current trend. Thus the entire project of
Blood Donor System is clearly tested, all the modules are working correctly, as well as
the output is verified.
BIBLIOGRAPHY
1. Professional ASP.NET 1.0, Special Edition
Author(s): Alex Homer, Brian Francis, David Sussman, Karli Watson, Richard Anderson
and Robert Howard
Released: February 2002
Publisher: Wrox Press
2. eXtreme .NET: Introducing eXtreme Programming Techniques to .NET
Developers
Author(s): Dr. Neil Roodyn
Released: November 2004
Publisher: Addison-Wesley
3. Student's Essential Guide to .NET, 1st Edition
Author(s): Tony Grimer
Released: October 2004
Publisher: Butterworth-Heinemann
4. Professional DotNetNuke ASP.NET Portals
Author(s): Shaun Walker, Patrick J. Santry, Joe Brinkman, Dan Caron, Scott McCulloch,
Scott Willhite, Bruce Hopkins
Released: June 2005
Publisher: wrox press.

Blood Donor's Management System

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Blood Donor's Management System

Загружено:

Авторское право:

Доступные форматы

Blood Donors Management System

Pentium IV 2.4 GHz.

BLOOD GROUP MASTER:

SCREENS & CODINGS:

protected void Page_Load(object sender, EventArgs

S2 = "Select * From Batch";

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

protected void Page_Load(object sender, EventArgs

protected void Page_Load(object sender, EventArgs

S = "Update DeptMstr Set DName='" +

public void Disp()

S = "Select MAX(BID) From Batch";

protected void Page_Load(object sender, EventArgs

ASP.NET Technology Backgrounder

ASP.NET Page Framework and the Web Forms Page

XML Web Services

State Management Facilities

independent of any controls on the page. It can be shared between

schemes for Web applications. You can easily remove, add to or

A process model that is improved over ASP.

Compiling requested pages and storing them on the server

ASP.NET-specific performance counters.

Web application testing tools.

Performance Counter Support

ASP.NET System performance counter group.

ASP.NET Application performance counter group.

The ASP.NET system group is accessible through the Performance Monitor

Integrating with IIS

ASP.NET authentication provider

credentials and submits the form. If

request, the system issues a form that

authenticated and authorized by an

provided by Microsoft that offers a

USING ASP.NET CONFIGURATION FILES

ASP.NET Data Access

advantages over ADO disconnected record sets. Whereas ADO requires

Working with a Single Table

Working with Multiple Database Tables

Displaying Data in a Control

ASP.NET Web Application Security

Windows: Basic, digest, or Integrated Windows Authentication

Microsoft Passport Authentication

ASP.NET controls access to site information by comparing authenticated

ASP.NET Data Access

Working with a Single Table

Working with Multiple Database Tables

Displaying Data in a Control

ASP.NET Web Application Security

Windows: Basic, digest, or Integrated Windows Authentication

Microsoft Passport Authentication

ASP.NET controls access to site information by comparing authenticated credentials, or

An improved process model

Compilation of requested pages and automatic storage on the

ASP.NET-specific performance counters

Web application testing tools

Applications used to run a small business

Corporations- wide applications

Front-end for enterprise-wide client/server applications

Main Elements of Access

New Features in MS Access

New objects, properties , methods and others language elements

Accessing the Internet or an intranet from your applicaions

Creating custom objects with class modules.