Академический Документы
Профессиональный Документы
Культура Документы
SCHOOL MANAGEMENT
SYSTEM
2
ABSTRACT
3
School Management System is a large database system which can be used for managing
your school's day to day business. School Management System allows users to store almost
all of their school's information electronically, including information on students,
properties, teaching meteorites etc. Most importantly, this information can be easily shared
with authorized users, records can be easily searched, and reports can be easily generated.
School Management System is software which is helpful for students as well as the
school authorities. In the current system all the activities are done manually. It is very time
consuming and costly. Our School Management System deals with the various activities
related to the students.
There are mainly 3 modules in this software
User module
Student Module
Mark management
In the Software we can register as a user and user has of two types, student and
administrator. Administrator has the power to add new user and can edit and delete a user.
A student can register as user and can add edit and delete his profile. The administrator can
add edit and delete marks for the student. All the users can see the marks.
4
CHAPTER 1
I N T R O D U C T I O N
5
Introduction:
School management system that provides following facilities search for student with
register number and name, add student, edit student details, delete student details, marks
and remarks. Language used is C# and db is SQL server 2000 and SQL Client has been
used in code.
One Student Master is already there once db is installed with user name and register
number.
Its very good project where in all the events of all forms have been handled in Globals.cs
that acts as business and data access layer. All DB interactions are in this file only.. The
authentication and authorization was crosschecked at all the relevant stages. The user level
accessibility has been restricted into two zones namely. The student master zone and the
normal student zone.
About the Organization
School Management System will deal in all the requirements needed for managing School.
It will deal with the process of maintaining data about the students and many other things as
well as admissions, extracurricular, Family, marks and remark for school students .
Manual Process
Visit The
Student master school Search for student with name
management or register number
system
Leaves
the
student Get the marks and results for
Add/edit/delete student details
manage students
ment
system
6
ANALYSIS
During analysis, data collected on the various files, decision points and transactions
handled by the present system. The commonly used tools in the system are Data Flow
Diagram, interviews, etc. Training, experience and common sense are required for collection
of relevant information needed to develop the system. The success of the system depends
largely on how clearly the problem is defined, thoroughly investigated and properly carried
out through the choice of solution. A good analysis model should provide not only the
mechanisms of problem understanding but also the frame work of the solution. Thus it
should be studied thoroughly by collecting data about the system. Then the proposed system
should be analyzed thoroughly in accordance with the needs.
In the current system we need to keep a number of records related to the student and
want to enter the details of the student and the marks manually. In this system only the
teacher or the school authority views the mark of the student and they want to enter the
details of the student. This is time consuming and has much cost.
In our proposed system we have the provision for adding the details of the
students by themselves. So the overhead of the school authorities and the teachers is become
\less. Another advantage of the system is that it is very easy to edit the details of the student
and delete a student when it found unnecessary. The marks of the student are added in the
database and so students can also view the marks whenever they want. Our proposed system has
several advantages
All the manual difficulties in managing the student details in a school or college
have been rectified by implementing computerization.
8
CHAPTER 2
S Y S T E M R E Q U I R E M E N T S
9
SYSTEM REQUIREMENTS
For Windows 95 based computers , a 486 / 66 MHz or higher processor with 8MB of
RAM
For Windows 98 based computers , a 500/88MHz or higher processor with 32 Mb of
RAM
For Windows NT based computers , a 488 / 66 MHz or higher processor with 16 MB
of RAM
For Windows 200 based computers , a 700/850 MHz or higher processor with 512 MB
of Ram
Hardware Requirements
Pentium IV Processor.
128 MB RAM.
Software Requirements
CHAPTER 3
MODULES
11
Modules:
The system after careful analysis has been identified to be presented with the
modules.
1. Administrator module: The module manages the information of all the members
who practically exist for this organization. Each member is exclusively associated
with a specific department and authorized designation. The module manages all the
transactional relations that generically arise as and when the system has been
executed, upon the requirements. In this Admin can able to change the password.
2. Members(Users) information module: The module maintains the actual members
list that have availed books upon this system. Users can find items, change profile
details, etc., from their homes as the library’s transactions are online. In this module
the user can have limited actions.
3. Search/Issue Book module: This module maintains the information related to
searching for the Books with types and Issue the books Search/Issue Books page
accessed from actions page, in this page search and issue is done. First user enters the
criteria for book searching and a book is successfully find than user can select the
book he wishes to get issued in grid and get it issued.
4. Manage Categories module: This module maintains the information related to Add
categories and Edit categories. It can have the description and status of categories.
5. Add/Remove books module: This module maintains the information related to
add/remove issues by the admin. For adding there should be at least one category
.Books can be removed, all books in system are shown in Remove books section user
can use Remove button to remove books after setting Quantity to be removed of book
selected.
12
CHAPTER4
S Y S T E M A N A L Y S I S
13
SYSTEM ANALYSIS:
3.2 GUI’S
In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browses interface. The GUI’S at the top level have been categorized
The Student Master interface concentrate on the A Secure and easy to share database. An
efficient Student Management Solution that, enables in maintaining and give the promotions and
remarks for the student in the School management system.
The .NET Framework has two main components: the common language
runtime and the .NET Framework class library. The common language
runtime is the foundation of the .NET Framework. You can think of the
runtime as an agent that manages code at execution time, providing core
services such as memory management, thread management, and remoting,
while also enforcing strict type safety and other forms of code accuracy
that ensure security and robustness. In fact, the concept of code
management is a fundamental principle of the runtime. Code that targets
the runtime is known as managed code, while code that does not target the
runtime is known as unmanaged code. The class library, the other main
component of the .NET Framework, is a comprehensive, object-oriented
collection of reusable types that you can use to develop applications
ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by
ASP.NET, such as Web Forms and XML Web services.
The runtime enforces code access security. For example, users can trust
that an executable embedded in a Web page can play an animation on
16
screen or sing a song, but cannot access their personal data, file system, or
network. The security features of the runtime thus enable legitimate
Internet-deployed software to be exceptionally feature rich.
While the runtime is designed for the software of the future, it also
supports software of today and yesterday. Interoperability between
managed and unmanaged code enables developers to continue to use
necessary COM components and DLLs.
17
Defines rules that languages must follow, which helps ensure that objects
written in different languages can interact with each other.
Describes concepts and defines terms relating to the common type system.
18
Type Definitions
Type Members
Describes events, fields, nested types, methods, and properties, and
concepts such as member overloading, overriding, and inheritance.
Value Types
Classes
Delegates
Arrays
Interfaces
Pointers
Related Sections
Describes the run-time environment that manages the execution of code and
provides application development services.
Cross-Language Interoperability
This section describes the common language runtime's built-in support for
language interoperability and explains the role that the CLS plays in
enabling guaranteed cross-language interoperability. CLS features and
rules are identified and CLS compliance is discussed.
In This Section
Language Interoperability
Explains the need for a set of features common to all languages and
identifies CLS rules and features.
Describes how types are declared, used, and managed by the common
language runtime.
Console applications.
ASP.NET applications.
Windows services.
The Windows Forms classes contained in the .NET Framework are designed
to be used for GUI development. You can easily create command windows,
buttons, menus, toolbars, and other screen elements with the flexibility
necessary to accommodate shifting business needs.
through the Web. Your applications can implement the features of a local
application while being deployed like a Web page.
Choosing a Complier
To obtain the benefits provided by the common language runtime, you must
use one or more language compilers that target the runtime.
Compiling translates your source code into MSIL and generates the
required metadata.
Assemblies Overview
It forms a type boundary. Every type's identity includes the name of the
assembly in which it resides. A type called MyType loaded in the scope of
one assembly is not the same as a type called MyType loaded in the scope
of another assembly.
There are several ways to create assemblies. You can use development
tools, such as Visual Studio .NET, that you have used in the past to
create .dll or .exe files. You can use tools provided in the .NET Framework
SDK to create assemblies with modules created in other development
environments. You can also use common language runtime APIs, such as
Reflection. Emit, to create dynamic assemblies.
If you have used earlier versions of ASP technology, you will immediately
notice the improvements that ASP.NET and Web Forms offers. For
example, you can develop Web Forms pages in any language that supports
the .NET Framework. In addition, your code no longer needs to share the
same file with your HTTP text (although it can continue to do so if you
prefer). Web Forms pages execute in native machine language because, like
any other managed application, they take full advantage of the runtime. In
contrast, unmanaged ASP pages are always scripted and interpreted.
ASP.NET pages are faster, more functional, and easier to develop than
unmanaged ASP pages because they interact with the runtime like any
managed application.
27
The .NET Framework also provides a collection of classes and tools to aid
in development and consumption of XML Web services applications. XML
Web services are built on standards such as SOAP (a remote procedure-call
protocol), XML (an extensible data format), and WSDL (the Web Services
Description Language). The .NET Framework is built on these standards to
promote interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the
Web, parse its WSDL description, and produce C# or Visual Basic source
code that your application can use to become a client of the XML Web
service. The source code can create classes derived from classes in the
class library that handle all the underlying communication using SOAP and
XML parsing. Although you can use the class library to consume XML Web
services directly, the Web Services Description Language tool and the
other tools contained in the SDK facilitate your development efforts with
the .NET Framework.
If you develop and publish your own XML Web service, the .NET
Framework provides a set of classes that conform to all the underlying
communication standards, such as SOAP, WSDL, and XML. Using those
classes enables you to focus on the logic of your service, without
concerning yourself with the communications infrastructure required by
distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web
service will run with the speed of native machine language using the
scalable communication of IIS.
This section describes the programming essentials you need to build .NET
applications, from creating assemblies from your code to securing your
28
Describes the ADO.NET architecture and how to use the ADO.NET classes
to manage application data and interact with data sources including
Microsoft SQL Server, OLE DB data sources, and XML.
Shows how to use Internet access classes to implement both Web- and
Internet-based applications.
Developing Components
Explains the .NET Framework SDK mechanism called the Code Document
Object Model (CodeDOM) that enables the output of source code in
multiple programming languages.
Explains the concept of a runtime host, which loads the runtime into a
process, creates the application domain within the process, and loads and
executes user code.
Processing Transactions
Discusses how the garbage collector manages memory and how you can
program to use memory more efficiently.
31
Describes how to create and work with assemblies and application domains.
Securing Applications
Serializing Objects
Discusses how to use performance counters and event logs with your
application.
Threading
Explains the runtime support for threading and how to program using
various synchronization techniques.
Discusses formatting and parsing base data types and using regular
expressions to process text.
Explains how you can perform synchronous and asynchronous file and data
stream access and how to use to isolated storage.
Introduction to 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.
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 you to build powerful forms-based Web pages. When
building these pages, you can use ASP.NET server controls to create
common UI elements, and program them for common tasks. These controls
allow you to rapidly build a Web Form out of reusable built-in or custom
components, simplifying the code of a page. For more information, see Web
Forms Pages. For information on how to develop ASP.NET server controls,
see Developing ASP.NET Server Controls
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. These features and how you can use them are outlined as
follows:
34
If you have ASP development skills, the new ASP.NET programming model
will seem very familiar to you. However, the ASP.NET object model has
changed significantly from ASP, making it more structured and object-
oriented. Unfortunately this means that ASP.NET is not fully backward
compatible; almost all existing ASP pages will have to be modified to some
extent in order to run under ASP.NET. In addition, major changes to Visual
Basic .NET mean that existing ASP pages written with Visual Basic
Scripting Edition typically will not port directly to ASP.NET. In most
cases, though, the necessary changes will involve only a few lines of code.
For more information, see Migrating from ASP to ASP.NET
For advanced developers who want to use APIs as powerful as the ISAPI
programming interfaces that were included with previous versions of ASP,
ASP.NET offers the IHttpHandler and IHttpModule interfaces.
35
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 Trace
Context class, which allows you to write custom debug statements to your
pages as you 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
36
viewer that is stored in the root directory of your application. For more
information, see ASP.NET Trace
Building Applications
Describes writing applications that use the system console for input and
output.
Deploying Applications
Shows how to use the .NET Framework and the common language runtime
to create self-described, self-contained applications.
Configuring Applications
generate the most frequently executed code, and how much time it takes to
execute them.
Enabling Profiling
When you create Web Forms pages, you can use these types of controls:
HTML server controls HTML elements exposed to the server so you can
program them. HTML server controls expose an object model that maps
very closely to the HTML elements that they render.
Web server controls Controls with more built-in features than HTML
server controls. Web server controls include not only form-type controls
such as buttons and text boxes, but also special-purpose controls such as a
calendar. Web server controls are more abstract than HTML server controls
in that their object model does not necessarily reflect HTML syntax.
User controls Controls that you create as Web Forms pages. You can
embed Web Forms user controls in other Web Forms pages, which is an
easy way to create menus, toolbars, and other reusable elements.
You can use all types of controls on the same page. The following sections
provide more detail about ASP.NET server controls. For more information
about validation controls, see Web Forms Validation for information about
user controls; see Introduction to Web User Controls
40
HTML server controls are HTML elements containing attributes that make
them visible to — and programmable on — the server. By default, HTML
elements on a Web Forms page are not available to the server; they are
treated as opaque text that is passed through to the browser. However, by
converting HTML elements to HTML server controls, you expose them as
elements you can program on the server.
The object model for HTML server controls maps closely to that of the
corresponding elements. For example, HTML attributes are exposed in
HTML server controls as properties.
The page framework provides predefined HTML server controls for the
HTML elements most commonly used dynamically on a page: forms, the
HTML <INPUT> elements (text box, check box, Submit button, and so on),
list box (<SELECT>), table, image, and so on. These predefined HTML
server controls share the basic properties of the generic control, and in
addition, each control typically provides its own set of properties and its
own event.
41
An object model that you can program against on the server using the
familiar object-oriented techniques. Each server control exposes properties
that allow you to manipulate the control's HTML attributes
programmatically in server code.
A set of events for which you can write event handlers in much the same
way you would in a client-based form, except that the event is handled in
server code.
Interaction with validation controls you can easily verify that a user has
entered appropriate information into a control.
Web server controls are a second set of controls designed with a different
emphasis. They do not map one-to-one to HTML server controls. Instead,
they are defined as abstract controls in which the actual HTML rendered by
the control can be quite different from the model that you program against.
For example, a RadioButtonList Web server control might be rendered in a
table or as inline text with other HTML.
Web server controls include traditional form controls such as buttons and
text boxes as well as complex controls such as tables. They also include
controls that provide commonly used form functionality such as displaying
data in a grid, choosing dates, and so on.
42
Web server controls offer all of the features described above for HTML
server controls (except one-to-one mapping to HTML elements) and these
additional features:
For some controls, the ability to define your own look for the control using
templates
For some controls, the ability to specify whether a control's event causes
immediate posting to the server or is instead cached and raised when the
form is submitted.
At design time in HTML view, the controls appear in your page in a format
such as:
The attributes in this case are not those of HTML elements. Instead, they
are properties of the Web control.
When the Web Forms page runs, the Web server control is rendered on the
page using appropriate HTML, which often depends not only on the browser
type but also on settings that you have made for the control. For example, a
Textbox control might render as an <INPUT> tag or a <TEXTAREA> tag,
depending on its properties.
43
D e s i g n
44
UML DESIGNS
ER-Diagrams
• The set of primary components that are identified by the ERD are
2. A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set of
diagram, which is as follows.
In this the structural and behavioral as parts of the system are represented as
they are to be built.
In this the structural and behavioral aspects of the environment in which the system is to
be implemented are represented.
UML Analysis modeling, which focuses on the user model and structural model
views of the system.
Databases used
View
student
information
Add details
for students
Student
master Save the
updated data
of students
View the
promotions
Marks and
remarks
47
CHAPTER 5
CODE
48
using System;
using System.Collections;
using System.ComponentModel;
using System.Drawing;
using System.Data;
using System.Data.OleDb;
using System.Windows.Forms;
namespace StudentManagementSystem
{
/// <summary>
/// Summary description for StudentDetails.
/// </summary>
public class StudentDetails : System.Windows.Forms.UserControl
{
private System.Windows.Forms.GroupBox grpControls;
public System.Windows.Forms.DataGrid grdStudent;
private System.Windows.Forms.Button btnClose;
private System.Windows.Forms.Button btnSave;
private System.Windows.Forms.Button btnDelete;
private System.Windows.Forms.Button btnEdit;
private System.Windows.Forms.Button btnAdd;
private System.Windows.Forms.DataGridTableStyle
dataGridTableStyle1;
private System.Windows.Forms.Panel panel1;
private System.Windows.Forms.TextBox txtSearchByRegNo;
public System.Windows.Forms.TextBox txtSearchByName;
private System.Windows.Forms.Label label1;
private System.Windows.Forms.Label label2;
private System.Windows.Forms.DataGridTextBoxColumn
dataGridTextBoxColumn7;
private System.Windows.Forms.DataGridTextBoxColumn
dataGridTextBoxColumn8;
private System.Windows.Forms.DataGridTextBoxColumn
dataGridTextBoxColumn9;
private System.Windows.Forms.TabControl tabControl1;
private System.Windows.Forms.TabPage tbpPersonel;
private System.Windows.Forms.TabPage tbpAdmission;
private System.Windows.Forms.TabPage tbpFamily;
private System.Windows.Forms.TabPage tbpMarks;
private System.Windows.Forms.GroupBox grpField;
private System.Windows.Forms.TextBox txtHomepage;
private System.Windows.Forms.Label label16;
private System.Windows.Forms.TextBox txtEmail;
private System.Windows.Forms.TextBox txtPhone;
private System.Windows.Forms.Label label9;
private System.Windows.Forms.Label label10;
private System.Windows.Forms.Label label12;
private System.Windows.Forms.TextBox txtAddress;
public System.Windows.Forms.TextBox txtName;
private System.Windows.Forms.Label label7;
49
public StudentDetails()
{
// This call is required by the Windows.Forms Form
Designer.
50
InitializeComponent();
/// <summary>
/// Clean up any resources being used.
/// </summary>
protected override void Dispose( bool disposing )
{
if( disposing )
{
if(components != null)
{
components.Dispose();
}
}
base.Dispose( disposing );
}
this.dtBirthDate = new
System.Windows.Forms.DateTimePicker();
this.txtHomepage = new System.Windows.Forms.TextBox();
this.label16 = new System.Windows.Forms.Label();
this.txtEmail = new System.Windows.Forms.TextBox();
this.txtPhone = new System.Windows.Forms.TextBox();
this.label9 = new System.Windows.Forms.Label();
this.label10 = new System.Windows.Forms.Label();
this.label12 = new System.Windows.Forms.Label();
this.txtAddress = new System.Windows.Forms.TextBox();
this.txtName = new System.Windows.Forms.TextBox();
this.label7 = new System.Windows.Forms.Label();
this.label4 = new System.Windows.Forms.Label();
this.tbpFamily = new System.Windows.Forms.TabPage();
this.groupBox6 = new System.Windows.Forms.GroupBox();
this.groupBox2 = new System.Windows.Forms.GroupBox();
this.txtFatherOfficePhone = new
System.Windows.Forms.TextBox();
this.label6 = new System.Windows.Forms.Label();
this.label15 = new System.Windows.Forms.Label();
this.txtFatherCellPhone = new
System.Windows.Forms.TextBox();
this.txtFather = new System.Windows.Forms.TextBox();
this.label13 = new System.Windows.Forms.Label();
this.groupBox1 = new System.Windows.Forms.GroupBox();
this.txtMotherCellPhone = new
System.Windows.Forms.TextBox();
this.label23 = new System.Windows.Forms.Label();
this.label11 = new System.Windows.Forms.Label();
this.txtMotherOfficePhone = new
System.Windows.Forms.TextBox();
this.label24 = new System.Windows.Forms.Label();
this.txtMother = new System.Windows.Forms.TextBox();
this.groupBox3 = new System.Windows.Forms.GroupBox();
this.txtResidenceAddress = new
System.Windows.Forms.TextBox();
this.label26 = new System.Windows.Forms.Label();
this.label25 = new System.Windows.Forms.Label();
this.txtResPhone = new System.Windows.Forms.TextBox();
this.tbpAdmission = new
System.Windows.Forms.TabPage();
this.grpAdmission = new
System.Windows.Forms.GroupBox();
this.groupBox5 = new System.Windows.Forms.GroupBox();
this.txtAdmittedBy = new
System.Windows.Forms.TextBox();
this.label8 = new System.Windows.Forms.Label();
this.dtAdmissionDate = new
System.Windows.Forms.DateTimePicker();
this.label18 = new System.Windows.Forms.Label();
this.groupBox4 = new System.Windows.Forms.GroupBox();
this.label19 = new System.Windows.Forms.Label();
this.txtPrevSchool = new
System.Windows.Forms.TextBox();
this.txtPrevSchoolAddress = new
System.Windows.Forms.TextBox();
this.label22 = new System.Windows.Forms.Label();
52
this.txtPrevSchoolPhone = new
System.Windows.Forms.TextBox();
this.label21 = new System.Windows.Forms.Label();
this.txtReasonForLeaving = new
System.Windows.Forms.TextBox();
this.label20 = new System.Windows.Forms.Label();
this.tbpCurricular = new
System.Windows.Forms.TabPage();
this.groupBox7 = new System.Windows.Forms.GroupBox();
this.txtRegNo = new System.Windows.Forms.TextBox();
this.cmbBatch = new System.Windows.Forms.ComboBox();
this.label5 = new System.Windows.Forms.Label();
this.label3 = new System.Windows.Forms.Label();
this.tbpExtraCurricular = new
System.Windows.Forms.TabPage();
this.tbpPromotion = new
System.Windows.Forms.TabPage();
this.tbpMarks = new System.Windows.Forms.TabPage();
this.tbpRemarks = new System.Windows.Forms.TabPage();
this.txtRemarks = new System.Windows.Forms.TextBox();
this.grpControls.SuspendLayout();
((System.ComponentModel.ISupportInitialize)
(this.grdStudent)).BeginInit();
this.panel1.SuspendLayout();
this.tabControl1.SuspendLayout();
this.tbpPersonel.SuspendLayout();
this.grpField.SuspendLayout();
this.tbpFamily.SuspendLayout();
this.groupBox6.SuspendLayout();
this.groupBox2.SuspendLayout();
this.groupBox1.SuspendLayout();
this.groupBox3.SuspendLayout();
this.tbpAdmission.SuspendLayout();
this.grpAdmission.SuspendLayout();
this.groupBox5.SuspendLayout();
this.groupBox4.SuspendLayout();
this.tbpCurricular.SuspendLayout();
this.groupBox7.SuspendLayout();
this.tbpRemarks.SuspendLayout();
this.SuspendLayout();
//
// grpControls
//
this.grpControls.Controls.Add(this.btnCancel);
this.grpControls.Controls.Add(this.grdStudent);
this.grpControls.Controls.Add(this.btnClose);
this.grpControls.Controls.Add(this.btnSave);
this.grpControls.Controls.Add(this.btnDelete);
this.grpControls.Controls.Add(this.btnEdit);
this.grpControls.Controls.Add(this.btnAdd);
this.grpControls.Dock =
System.Windows.Forms.DockStyle.Fill;
this.grpControls.FlatStyle =
System.Windows.Forms.FlatStyle.System;
this.grpControls.Location = new
System.Drawing.Point(0, 0);
this.grpControls.Name = "grpControls";
53
this.dataGridTableStyle1});
this.grdStudent.CurrentCellChanged += new
System.EventHandler(this.grdStudent_CurrentCellChanged);
//
// dataGridTableStyle1
//
this.dataGridTableStyle1.DataGrid = this.grdStudent;
this.dataGridTableStyle1.GridColumnStyles.AddRange(new
System.Windows.Forms.DataGridColumnStyle[] {
this.dataGridTextBoxColumn7,
this.dataGridTextBoxColumn8,
54
this.dataGridTextBoxColumn9});
this.dataGridTableStyle1.HeaderForeColor =
System.Drawing.SystemColors.ControlText;
this.dataGridTableStyle1.MappingName = "Student";
this.dataGridTableStyle1.ReadOnly = true;
//
// dataGridTextBoxColumn7
//
this.dataGridTextBoxColumn7.Format = "";
this.dataGridTextBoxColumn7.FormatInfo = null;
this.dataGridTextBoxColumn7.MappingName = "Id";
this.dataGridTextBoxColumn7.NullText = "";
this.dataGridTextBoxColumn7.ReadOnly = true;
this.dataGridTextBoxColumn7.Width = 0;
//
// dataGridTextBoxColumn8
//
this.dataGridTextBoxColumn8.Format = "";
this.dataGridTextBoxColumn8.FormatInfo = null;
this.dataGridTextBoxColumn8.HeaderText = "Register
No:";
this.dataGridTextBoxColumn8.MappingName = "RegNo";
this.dataGridTextBoxColumn8.NullText = "";
this.dataGridTextBoxColumn8.ReadOnly = true;
this.dataGridTextBoxColumn8.Width = 75;
//
// dataGridTextBoxColumn9
//
this.dataGridTextBoxColumn9.Format = "";
this.dataGridTextBoxColumn9.FormatInfo = null;
this.dataGridTextBoxColumn9.HeaderText = "Name";
this.dataGridTextBoxColumn9.MappingName =
"StudentName";
this.dataGridTextBoxColumn9.NullText = "";
this.dataGridTextBoxColumn9.ReadOnly = true;
this.dataGridTextBoxColumn9.Width = 250;
//
// btnClose
//
this.btnClose.Location = new
System.Drawing.Point(616, 16);
this.btnClose.Name = "btnClose";
this.btnClose.Size = new System.Drawing.Size(78, 32);
this.btnClose.TabIndex = 4;
this.btnClose.Text = "&Close";
this.btnClose.Click += new
System.EventHandler(this.btnClose_Click);
//
// btnSave
//
this.btnSave.Location = new System.Drawing.Point(431,
16);
this.btnSave.Name = "btnSave";
this.btnSave.Size = new System.Drawing.Size(78, 32);
this.btnSave.TabIndex = 3;
55
this.btnSave.Text = "&Save";
this.btnSave.Click += new
System.EventHandler(this.btnSave_Click);
//
// btnDelete
//
this.btnDelete.Location = new
System.Drawing.Point(319, 16);
this.btnDelete.Name = "btnDelete";
this.btnDelete.Size = new System.Drawing.Size(78, 32);
this.btnDelete.TabIndex = 2;
this.btnDelete.Text = "&Delete";
this.btnDelete.Click += new
System.EventHandler(this.btnDelete_Click);
//
// btnEdit
//
this.btnEdit.Location = new System.Drawing.Point(215,
16);
this.btnEdit.Name = "btnEdit";
this.btnEdit.Size = new System.Drawing.Size(78, 32);
this.btnEdit.TabIndex = 1;
this.btnEdit.Text = "&Edit";
this.btnEdit.Click += new
System.EventHandler(this.btnEdit_Click);
//
// btnAdd
//
this.btnAdd.Location = new System.Drawing.Point(103,
16);
this.btnAdd.Name = "btnAdd";
this.btnAdd.Size = new System.Drawing.Size(72, 32);
this.btnAdd.TabIndex = 0;
this.btnAdd.Text = "&Add";
this.btnAdd.Click += new
System.EventHandler(this.btnAdd_Click);
//
// panel1
//
this.panel1.BackColor =
System.Drawing.Color.AliceBlue;
this.panel1.BorderStyle =
System.Windows.Forms.BorderStyle.FixedSingle;
this.panel1.Controls.Add(this.txtSearchByRegNo);
this.panel1.Controls.Add(this.txtSearchByName);
this.panel1.Controls.Add(this.label1);
this.panel1.Controls.Add(this.label2);
this.panel1.Dock =
System.Windows.Forms.DockStyle.Bottom;
this.panel1.Location = new System.Drawing.Point(0,
283);
this.panel1.Name = "panel1";
this.panel1.Size = new System.Drawing.Size(800, 34);
this.panel1.TabIndex = 14;
//
// txtSearchByRegNo
//
56
this.txtSearchByRegNo.Location = new
System.Drawing.Point(434, 5);
this.txtSearchByRegNo.Name = "txtSearchByRegNo";
this.txtSearchByRegNo.Size = new
System.Drawing.Size(144, 20);
this.txtSearchByRegNo.TabIndex = 1;
this.txtSearchByRegNo.Text = "";
this.txtSearchByRegNo.TextChanged += new
System.EventHandler(this.txtSearchByRegNo_TextChanged);
//
// txtSearchByName
//
this.txtSearchByName.Location = new
System.Drawing.Point(106, 5);
this.txtSearchByName.Name = "txtSearchByName";
this.txtSearchByName.Size = new
System.Drawing.Size(144, 20);
this.txtSearchByName.TabIndex = 0;
this.txtSearchByName.Text = "";
this.txtSearchByName.TextChanged += new
System.EventHandler(this.txtSearchByName_TextChanged);
//
// label1
//
this.label1.Location = new System.Drawing.Point(10,
5);
this.label1.Name = "label1";
this.label1.Size = new System.Drawing.Size(104, 23);
this.label1.TabIndex = 5;
this.label1.Text = "Search By Name:";
//
// label2
//
this.label2.Location = new System.Drawing.Point(330,
5);
this.label2.Name = "label2";
this.label2.Size = new System.Drawing.Size(120, 23);
this.label2.TabIndex = 8;
this.label2.Text = "Search By Reg.No:";
//
// tabControl1
//
this.tabControl1.Controls.Add(this.tbpPersonel);
this.tabControl1.Controls.Add(this.tbpFamily);
this.tabControl1.Controls.Add(this.tbpAdmission);
this.tabControl1.Controls.Add(this.tbpCurricular);
this.tabControl1.Controls.Add(this.tbpExtraCurricular);
this.tabControl1.Controls.Add(this.tbpPromotion);
this.tabControl1.Controls.Add(this.tbpMarks);
this.tabControl1.Controls.Add(this.tbpRemarks);
this.tabControl1.Dock =
System.Windows.Forms.DockStyle.Bottom;
this.tabControl1.Location = new
System.Drawing.Point(0, 317);
this.tabControl1.Name = "tabControl1";
57
this.tabControl1.SelectedIndex = 0;
this.tabControl1.Size = new System.Drawing.Size(800,
235);
this.tabControl1.TabIndex = 15;
//
// tbpPersonel
//
this.tbpPersonel.Controls.Add(this.grpField);
this.tbpPersonel.Location = new
System.Drawing.Point(4, 22);
this.tbpPersonel.Name = "tbpPersonel";
this.tbpPersonel.Size = new System.Drawing.Size(792,
209);
this.tbpPersonel.TabIndex = 0;
this.tbpPersonel.Text = "Personal";
//
// grpField
//
this.grpField.BackColor =
System.Drawing.Color.AliceBlue;
this.grpField.Controls.Add(this.dtBirthDate);
this.grpField.Controls.Add(this.txtHomepage);
this.grpField.Controls.Add(this.label16);
this.grpField.Controls.Add(this.txtEmail);
this.grpField.Controls.Add(this.txtPhone);
this.grpField.Controls.Add(this.label9);
this.grpField.Controls.Add(this.label10);
this.grpField.Controls.Add(this.label12);
this.grpField.Controls.Add(this.txtAddress);
this.grpField.Controls.Add(this.txtName);
this.grpField.Controls.Add(this.label7);
this.grpField.Controls.Add(this.label4);
this.grpField.Dock =
System.Windows.Forms.DockStyle.Fill;
this.grpField.Location = new System.Drawing.Point(0,
0);
this.grpField.Name = "grpField";
this.grpField.Size = new System.Drawing.Size(792,
209);
this.grpField.TabIndex = 14;
this.grpField.TabStop = false;
//
// dtBirthDate
//
this.dtBirthDate.CustomFormat = "dd / MMM / yyyy";
this.dtBirthDate.Format =
System.Windows.Forms.DateTimePickerFormat.Custom;
this.dtBirthDate.Location = new
System.Drawing.Point(384, 24);
this.dtBirthDate.Name = "dtBirthDate";
this.dtBirthDate.ShowCheckBox = true;
this.dtBirthDate.ShowUpDown = true;
this.dtBirthDate.TabIndex = 26;
//
// txtHomepage
//
58
this.txtHomepage.BackColor =
System.Drawing.Color.White;
this.txtHomepage.Location = new
System.Drawing.Point(384, 88);
this.txtHomepage.Name = "txtHomepage";
this.txtHomepage.Size = new System.Drawing.Size(192,
20);
this.txtHomepage.TabIndex = 12;
this.txtHomepage.Text = "";
//
// label16
//
this.label16.Location = new System.Drawing.Point(304,
96);
this.label16.Name = "label16";
this.label16.Size = new System.Drawing.Size(67, 23);
this.label16.TabIndex = 25;
this.label16.Text = "Home Page";
//
// txtEmail
//
this.txtEmail.BackColor = System.Drawing.Color.White;
this.txtEmail.Location = new
System.Drawing.Point(384, 56);
this.txtEmail.Name = "txtEmail";
this.txtEmail.Size = new System.Drawing.Size(192, 20);
this.txtEmail.TabIndex = 9;
this.txtEmail.Text = "";
//
// txtPhone
//
this.txtPhone.BackColor = System.Drawing.Color.White;
this.txtPhone.Location = new System.Drawing.Point(72,
160);
this.txtPhone.Name = "txtPhone";
this.txtPhone.Size = new System.Drawing.Size(184, 20);
this.txtPhone.TabIndex = 6;
this.txtPhone.Text = "";
//
// label9
//
this.label9.Location = new System.Drawing.Point(304,
64);
this.label9.Name = "label9";
this.label9.Size = new System.Drawing.Size(72, 16);
this.label9.TabIndex = 17;
this.label9.Text = "Email";
//
// label10
//
this.label10.Font = new
System.Drawing.Font("Microsoft Sans Serif", 8.25F,
System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point,
((System.Byte)(0)));
this.label10.Location = new System.Drawing.Point(304,
24);
this.label10.Name = "label10";
59
this.tbpFamily.BackColor =
System.Drawing.Color.AliceBlue;
this.tbpFamily.Controls.Add(this.groupBox6);
this.tbpFamily.Location = new System.Drawing.Point(4,
22);
this.tbpFamily.Name = "tbpFamily";
this.tbpFamily.Size = new System.Drawing.Size(792,
209);
this.tbpFamily.TabIndex = 2;
this.tbpFamily.Text = "Family";
//
// groupBox6
//
this.groupBox6.Controls.Add(this.groupBox2);
this.groupBox6.Controls.Add(this.groupBox1);
this.groupBox6.Controls.Add(this.groupBox3);
this.groupBox6.Dock =
System.Windows.Forms.DockStyle.Fill;
this.groupBox6.Location = new System.Drawing.Point(0,
0);
this.groupBox6.Name = "groupBox6";
this.groupBox6.Size = new System.Drawing.Size(792,
209);
this.groupBox6.TabIndex = 20;
this.groupBox6.TabStop = false;
//
// groupBox2
//
this.groupBox2.Controls.Add(this.txtFatherOfficePhone);
this.groupBox2.Controls.Add(this.label6);
this.groupBox2.Controls.Add(this.label15);
this.groupBox2.Controls.Add(this.txtFatherCellPhone);
this.groupBox2.Controls.Add(this.txtFather);
this.groupBox2.Controls.Add(this.label13);
this.groupBox2.Location = new System.Drawing.Point(8,
16);
this.groupBox2.Name = "groupBox2";
this.groupBox2.Size = new System.Drawing.Size(264,
136);
this.groupBox2.TabIndex = 18;
this.groupBox2.TabStop = false;
this.groupBox2.Text = "Father";
//
// txtFatherOfficePhone
//
this.txtFatherOfficePhone.BackColor =
System.Drawing.Color.White;
this.txtFatherOfficePhone.Location = new
System.Drawing.Point(80, 64);
this.txtFatherOfficePhone.Name =
"txtFatherOfficePhone";
this.txtFatherOfficePhone.Size = new
System.Drawing.Size(166, 20);
this.txtFatherOfficePhone.TabIndex = 10;
this.txtFatherOfficePhone.Text = "";
61
//
// label6
//
this.label6.Location = new System.Drawing.Point(8,
32);
this.label6.Name = "label6";
this.label6.Size = new System.Drawing.Size(48, 16);
this.label6.TabIndex = 5;
this.label6.Text = "Name";
//
// label15
//
this.label15.Location = new System.Drawing.Point(8,
96);
this.label15.Name = "label15";
this.label15.Size = new System.Drawing.Size(64, 16);
this.label15.TabIndex = 11;
this.label15.Text = "Cell Phone";
//
// txtFatherCellPhone
//
this.txtFatherCellPhone.BackColor =
System.Drawing.Color.White;
this.txtFatherCellPhone.Location = new
System.Drawing.Point(80, 96);
this.txtFatherCellPhone.Name = "txtFatherCellPhone";
this.txtFatherCellPhone.Size = new
System.Drawing.Size(166, 20);
this.txtFatherCellPhone.TabIndex = 12;
this.txtFatherCellPhone.Text = "";
//
// txtFather
//
this.txtFather.BackColor = System.Drawing.Color.White;
this.txtFather.Location = new
System.Drawing.Point(80, 32);
this.txtFather.Name = "txtFather";
this.txtFather.Size = new System.Drawing.Size(166,
20);
this.txtFather.TabIndex = 6;
this.txtFather.Text = "";
//
// label13
//
this.label13.Location = new System.Drawing.Point(8,
64);
this.label13.Name = "label13";
this.label13.Size = new System.Drawing.Size(56, 16);
this.label13.TabIndex = 9;
this.label13.Text = "Off Phone";
//
// groupBox1
//
this.groupBox1.Controls.Add(this.txtMotherCellPhone);
this.groupBox1.Controls.Add(this.label23);
this.groupBox1.Controls.Add(this.label11);
62
this.groupBox1.Controls.Add(this.txtMotherOfficePhone);
this.groupBox1.Controls.Add(this.label24);
this.groupBox1.Controls.Add(this.txtMother);
this.groupBox1.Location = new
System.Drawing.Point(280, 16);
this.groupBox1.Name = "groupBox1";
this.groupBox1.Size = new System.Drawing.Size(272,
136);
this.groupBox1.TabIndex = 17;
this.groupBox1.TabStop = false;
this.groupBox1.Text = "Name";
//
// txtMotherCellPhone
//
this.txtMotherCellPhone.BackColor =
System.Drawing.Color.White;
this.txtMotherCellPhone.Location = new
System.Drawing.Point(88, 88);
this.txtMotherCellPhone.Name = "txtMotherCellPhone";
this.txtMotherCellPhone.Size = new
System.Drawing.Size(166, 20);
this.txtMotherCellPhone.TabIndex = 16;
this.txtMotherCellPhone.Text = "";
//
// label23
//
this.label23.Location = new System.Drawing.Point(16,
56);
this.label23.Name = "label23";
this.label23.Size = new System.Drawing.Size(56, 16);
this.label23.TabIndex = 13;
this.label23.Text = "Off Phone";
//
// label11
//
this.label11.Location = new System.Drawing.Point(16,
24);
this.label11.Name = "label11";
this.label11.Size = new System.Drawing.Size(64, 23);
this.label11.TabIndex = 7;
this.label11.Text = "Name";
//
// txtMotherOfficePhone
//
this.txtMotherOfficePhone.BackColor =
System.Drawing.Color.White;
this.txtMotherOfficePhone.Location = new
System.Drawing.Point(88, 56);
this.txtMotherOfficePhone.Name =
"txtMotherOfficePhone";
this.txtMotherOfficePhone.Size = new
System.Drawing.Size(166, 20);
this.txtMotherOfficePhone.TabIndex = 14;
this.txtMotherOfficePhone.Text = "";
//
63
// label24
//
this.label24.Location = new System.Drawing.Point(16,
88);
this.label24.Name = "label24";
this.label24.Size = new System.Drawing.Size(72, 16);
this.label24.TabIndex = 15;
this.label24.Text = "Cell Phone";
//
// txtMother
//
this.txtMother.BackColor = System.Drawing.Color.White;
this.txtMother.Location = new
System.Drawing.Point(88, 24);
this.txtMother.Name = "txtMother";
this.txtMother.Size = new System.Drawing.Size(166,
20);
this.txtMother.TabIndex = 8;
this.txtMother.Text = "";
//
// groupBox3
//
this.groupBox3.Controls.Add(this.txtResidenceAddress);
this.groupBox3.Controls.Add(this.label26);
this.groupBox3.Controls.Add(this.label25);
this.groupBox3.Controls.Add(this.txtResPhone);
this.groupBox3.Location = new
System.Drawing.Point(560, 16);
this.groupBox3.Name = "groupBox3";
this.groupBox3.Size = new System.Drawing.Size(296,
136);
this.groupBox3.TabIndex = 19;
this.groupBox3.TabStop = false;
this.groupBox3.Text = "Residence";
//
// txtResidenceAddress
//
this.txtResidenceAddress.BackColor =
System.Drawing.Color.White;
this.txtResidenceAddress.Location = new
System.Drawing.Point(80, 48);
this.txtResidenceAddress.Multiline = true;
this.txtResidenceAddress.Name = "txtResidenceAddress";
this.txtResidenceAddress.Size = new
System.Drawing.Size(184, 80);
this.txtResidenceAddress.TabIndex = 18;
this.txtResidenceAddress.Text = "";
//
// label26
//
this.label26.Location = new System.Drawing.Point(8,
48);
this.label26.Name = "label26";
this.label26.Size = new System.Drawing.Size(64, 17);
this.label26.TabIndex = 17;
this.label26.Text = "Address";
//
64
// label25
//
this.label25.Location = new System.Drawing.Point(8,
24);
this.label25.Name = "label25";
this.label25.Size = new System.Drawing.Size(64, 16);
this.label25.TabIndex = 15;
this.label25.Text = "Res Phone";
//
// txtResPhone
//
this.txtResPhone.BackColor =
System.Drawing.Color.White;
this.txtResPhone.Location = new
System.Drawing.Point(80, 24);
this.txtResPhone.Name = "txtResPhone";
this.txtResPhone.Size = new System.Drawing.Size(166,
20);
this.txtResPhone.TabIndex = 16;
this.txtResPhone.Text = "";
//
// tbpAdmission
//
this.tbpAdmission.Controls.Add(this.grpAdmission);
this.tbpAdmission.Location = new
System.Drawing.Point(4, 22);
this.tbpAdmission.Name = "tbpAdmission";
this.tbpAdmission.Size = new System.Drawing.Size(792,
209);
this.tbpAdmission.TabIndex = 1;
this.tbpAdmission.Text = "Admission";
//
// grpAdmission
//
this.grpAdmission.BackColor =
System.Drawing.Color.AliceBlue;
this.grpAdmission.Controls.Add(this.groupBox5);
this.grpAdmission.Controls.Add(this.groupBox4);
this.grpAdmission.Dock =
System.Windows.Forms.DockStyle.Fill;
this.grpAdmission.Location = new
System.Drawing.Point(0, 0);
this.grpAdmission.Name = "grpAdmission";
this.grpAdmission.Size = new System.Drawing.Size(792,
209);
this.grpAdmission.TabIndex = 0;
this.grpAdmission.TabStop = false;
//
// groupBox5
//
this.groupBox5.Controls.Add(this.txtAdmittedBy);
this.groupBox5.Controls.Add(this.label8);
this.groupBox5.Controls.Add(this.dtAdmissionDate);
this.groupBox5.Controls.Add(this.label18);
this.groupBox5.Location = new System.Drawing.Point(8,
16);
this.groupBox5.Name = "groupBox5";
65
//
// groupBox4
//
this.groupBox4.Controls.Add(this.label19);
this.groupBox4.Controls.Add(this.txtPrevSchool);
this.groupBox4.Controls.Add(this.txtPrevSchoolAddress);
this.groupBox4.Controls.Add(this.label22);
this.groupBox4.Controls.Add(this.txtPrevSchoolPhone);
this.groupBox4.Controls.Add(this.label21);
this.groupBox4.Controls.Add(this.txtReasonForLeaving);
this.groupBox4.Controls.Add(this.label20);
this.groupBox4.Location = new
System.Drawing.Point(264, 16);
this.groupBox4.Name = "groupBox4";
this.groupBox4.Size = new System.Drawing.Size(544,
176);
this.groupBox4.TabIndex = 28;
this.groupBox4.TabStop = false;
this.groupBox4.Text = "Previous Institute";
//
// label19
//
this.label19.Location = new System.Drawing.Point(16,
24);
this.label19.Name = "label19";
this.label19.Size = new System.Drawing.Size(56, 16);
this.label19.TabIndex = 2;
this.label19.Text = "Name";
//
// txtPrevSchool
//
this.txtPrevSchool.BackColor =
System.Drawing.Color.White;
this.txtPrevSchool.Location = new
System.Drawing.Point(80, 24);
this.txtPrevSchool.Name = "txtPrevSchool";
this.txtPrevSchool.Size = new
System.Drawing.Size(200, 20);
this.txtPrevSchool.TabIndex = 5;
this.txtPrevSchool.Text = "";
//
// txtPrevSchoolAddress
//
this.txtPrevSchoolAddress.BackColor =
System.Drawing.Color.White;
this.txtPrevSchoolAddress.Location = new
System.Drawing.Point(80, 48);
this.txtPrevSchoolAddress.Multiline = true;
this.txtPrevSchoolAddress.Name =
"txtPrevSchoolAddress";
this.txtPrevSchoolAddress.Size = new
System.Drawing.Size(200, 48);
this.txtPrevSchoolAddress.TabIndex = 9;
this.txtPrevSchoolAddress.Text = "";
//
67
// label22
//
this.label22.Location = new System.Drawing.Point(16,
48);
this.label22.Name = "label22";
this.label22.Size = new System.Drawing.Size(48, 24);
this.label22.TabIndex = 6;
this.label22.Text = "Address";
//
// txtPrevSchoolPhone
//
this.txtPrevSchoolPhone.BackColor =
System.Drawing.Color.White;
this.txtPrevSchoolPhone.Location = new
System.Drawing.Point(80, 104);
this.txtPrevSchoolPhone.Name = "txtPrevSchoolPhone";
this.txtPrevSchoolPhone.Size = new
System.Drawing.Size(136, 20);
this.txtPrevSchoolPhone.TabIndex = 10;
this.txtPrevSchoolPhone.Text = "";
//
// label21
//
this.label21.Location = new System.Drawing.Point(16,
104);
this.label21.Name = "label21";
this.label21.Size = new System.Drawing.Size(48, 16);
this.label21.TabIndex = 7;
this.label21.Text = "Phone";
//
// txtReasonForLeaving
//
this.txtReasonForLeaving.BackColor =
System.Drawing.Color.White;
this.txtReasonForLeaving.Location = new
System.Drawing.Point(296, 32);
this.txtReasonForLeaving.Multiline = true;
this.txtReasonForLeaving.Name = "txtReasonForLeaving";
this.txtReasonForLeaving.Size = new
System.Drawing.Size(240, 88);
this.txtReasonForLeaving.TabIndex = 11;
this.txtReasonForLeaving.Text = "";
//
// label20
//
this.label20.Location = new System.Drawing.Point(296,
16);
this.label20.Name = "label20";
this.label20.Size = new System.Drawing.Size(176, 16);
this.label20.TabIndex = 8;
this.label20.Text = "Reason For Leaving";
//
// tbpCurricular
//
this.tbpCurricular.BackColor =
System.Drawing.Color.AliceBlue;
this.tbpCurricular.Controls.Add(this.groupBox7);
68
this.tbpCurricular.Location = new
System.Drawing.Point(4, 22);
this.tbpCurricular.Name = "tbpCurricular";
this.tbpCurricular.Size = new
System.Drawing.Size(792, 209);
this.tbpCurricular.TabIndex = 7;
this.tbpCurricular.Text = "Academic";
//
// groupBox7
//
this.groupBox7.Controls.Add(this.txtRegNo);
this.groupBox7.Controls.Add(this.cmbBatch);
this.groupBox7.Controls.Add(this.label5);
this.groupBox7.Controls.Add(this.label3);
this.groupBox7.Dock =
System.Windows.Forms.DockStyle.Fill;
this.groupBox7.Location = new System.Drawing.Point(0,
0);
this.groupBox7.Name = "groupBox7";
this.groupBox7.Size = new System.Drawing.Size(792,
209);
this.groupBox7.TabIndex = 8;
this.groupBox7.TabStop = false;
//
// txtRegNo
//
this.txtRegNo.BackColor = System.Drawing.Color.White;
this.txtRegNo.Location = new
System.Drawing.Point(104, 24);
this.txtRegNo.Name = "txtRegNo";
this.txtRegNo.Size = new System.Drawing.Size(96, 20);
this.txtRegNo.TabIndex = 7;
this.txtRegNo.Text = "";
//
// cmbBatch
//
this.cmbBatch.BackColor = System.Drawing.Color.White;
this.cmbBatch.DropDownStyle =
System.Windows.Forms.ComboBoxStyle.DropDownList;
this.cmbBatch.Location = new
System.Drawing.Point(104, 56);
this.cmbBatch.Name = "cmbBatch";
this.cmbBatch.Size = new System.Drawing.Size(144, 21);
this.cmbBatch.TabIndex = 5;
//
// label5
//
this.label5.Location = new System.Drawing.Point(24,
56);
this.label5.Name = "label5";
this.label5.TabIndex = 4;
this.label5.Text = "Batch";
//
// label3
//
this.label3.Location = new System.Drawing.Point(24,
24);
69
this.label3.Name = "label3";
this.label3.TabIndex = 6;
this.label3.Text = "Register No:";
//
// tbpExtraCurricular
//
this.tbpExtraCurricular.BackColor =
System.Drawing.Color.AliceBlue;
this.tbpExtraCurricular.Location = new
System.Drawing.Point(4, 22);
this.tbpExtraCurricular.Name = "tbpExtraCurricular";
this.tbpExtraCurricular.Size = new
System.Drawing.Size(792, 209);
this.tbpExtraCurricular.TabIndex = 5;
this.tbpExtraCurricular.Text = "ExtraCurricular";
//
// tbpPromotion
//
this.tbpPromotion.BackColor =
System.Drawing.Color.AliceBlue;
this.tbpPromotion.Location = new
System.Drawing.Point(4, 22);
this.tbpPromotion.Name = "tbpPromotion";
this.tbpPromotion.Size = new System.Drawing.Size(792,
209);
this.tbpPromotion.TabIndex = 4;
this.tbpPromotion.Text = "Promotions";
//
// tbpMarks
//
this.tbpMarks.BackColor =
System.Drawing.Color.AliceBlue;
this.tbpMarks.Location = new System.Drawing.Point(4,
22);
this.tbpMarks.Name = "tbpMarks";
this.tbpMarks.Size = new System.Drawing.Size(792,
209);
this.tbpMarks.TabIndex = 3;
this.tbpMarks.Text = "Marks";
//
// tbpRemarks
//
this.tbpRemarks.Controls.Add(this.txtRemarks);
this.tbpRemarks.Location = new
System.Drawing.Point(4, 22);
this.tbpRemarks.Name = "tbpRemarks";
this.tbpRemarks.Size = new System.Drawing.Size(792,
209);
this.tbpRemarks.TabIndex = 6;
this.tbpRemarks.Text = "Remarks";
//
// txtRemarks
//
this.txtRemarks.BackColor =
System.Drawing.Color.White;
this.txtRemarks.Dock =
System.Windows.Forms.DockStyle.Fill;
70
this.txtRemarks.Location = new
System.Drawing.Point(0, 0);
this.txtRemarks.Multiline = true;
this.txtRemarks.Name = "txtRemarks";
this.txtRemarks.Size = new System.Drawing.Size(792,
209);
this.txtRemarks.TabIndex = 27;
this.txtRemarks.Text = "";
//
// StudentDetails
//
this.BackColor = System.Drawing.Color.AliceBlue;
this.Controls.Add(this.grpControls);
this.Controls.Add(this.panel1);
this.Controls.Add(this.tabControl1);
this.Name = "StudentDetails";
this.Size = new System.Drawing.Size(800, 552);
this.Load += new
System.EventHandler(this.StudentDetails_Load);
this.grpControls.ResumeLayout(false);
((System.ComponentModel.ISupportInitialize)
(this.grdStudent)).EndInit();
this.panel1.ResumeLayout(false);
this.tabControl1.ResumeLayout(false);
this.tbpPersonel.ResumeLayout(false);
this.grpField.ResumeLayout(false);
this.tbpFamily.ResumeLayout(false);
this.groupBox6.ResumeLayout(false);
this.groupBox2.ResumeLayout(false);
this.groupBox1.ResumeLayout(false);
this.groupBox3.ResumeLayout(false);
this.tbpAdmission.ResumeLayout(false);
this.grpAdmission.ResumeLayout(false);
this.groupBox5.ResumeLayout(false);
this.groupBox4.ResumeLayout(false);
this.tbpCurricular.ResumeLayout(false);
this.groupBox7.ResumeLayout(false);
this.tbpRemarks.ResumeLayout(false);
this.ResumeLayout(false);
}
#endregion
String connectionString =
System.Configuration.ConfigurationSettings.AppSettings["dsn"];
util.PopulateCombo( cmbBatch, connectionString,
"Batch", "BatchName", "BatchId", "1" );
LoadCurrentItem();
//// DisableFields();
//// LoadCurrentItem();
////
////
//// txtSearchByName.Focus();
//// btnSave.Enabled=false;
//// deleted="false";
}
txtHomepage.ReadOnly = readOnly;
txtEmail.ReadOnly = readOnly;
txtPhone.ReadOnly = readOnly;
txtAddress.ReadOnly = readOnly;
txtName.ReadOnly = readOnly;
txtAdmittedBy.ReadOnly = readOnly;
txtPrevSchool.ReadOnly = readOnly;
txtReasonForLeaving.ReadOnly = readOnly;
txtPrevSchoolPhone.ReadOnly = readOnly;
txtPrevSchoolAddress.ReadOnly = readOnly;
txtRemarks.ReadOnly = readOnly;
txtFather.ReadOnly = readOnly;
txtRegNo.ReadOnly = readOnly;
txtMother.ReadOnly = readOnly;
txtFatherOfficePhone.ReadOnly = readOnly;
txtFatherCellPhone.ReadOnly = readOnly;
txtMotherOfficePhone.ReadOnly = readOnly;
txtMotherCellPhone.ReadOnly = readOnly;
txtResPhone.ReadOnly = readOnly;
txtResidenceAddress.ReadOnly = readOnly;
cmbBatch.Enabled = enable;
dtBirthDate.Enabled = enable;
dtAdmissionDate.Enabled = enable;
txtSearchByRegNo.ReadOnly = enable;
txtSearchByName.ReadOnly = enable;
}
txtHomepage.Text = student.Homepage;
txtEmail.Text = student.Email;
txtPhone.Text = student.Phone;
txtAddress.Text = student.StudentAddress;
txtName.Text = student.StudentName;
txtAdmittedBy.Text = student.AdmittedBy;
txtPrevSchool.Text = student.PrevSchoolName;
txtReasonForLeaving.Text = student.ReasonForLeaving;
txtPrevSchoolPhone.Text = student.PrevSchoolPhone;
txtPrevSchoolAddress.Text = student.PrevSchoolAddress;
txtRemarks.Text = student.Remarks;
txtFather.Text = student.FatherName;
txtRegNo.Text = student.RegNo;
txtMother.Text = student.MotherName;
73
txtFatherOfficePhone.Text =
student.FatherOfficePhone;
txtFatherCellPhone.Text = student.FatherCellPhone;
txtMotherOfficePhone.Text = student.MotherResPhone;
txtMotherCellPhone.Text = student.MotherCellPhone;
txtResPhone.Text = student.ResidencePhone;
txtResidenceAddress.Text = student.ResidenceAddress;
cmbBatch.SelectedValue = student.BatchId;
dtAdmissionDate.Value = student.AdmissionDate;
dtAdmissionDate.Checked =
student.AdmissionDateSelected;
dtBirthDate.Value = student.DateOfBirth;
dtBirthDate.Checked = student.DateOfBirthSelected;
}
cmbBatch.SelectedIndex = 0;
dtAdmissionDate.Value = DateTime.Today;
dtAdmissionDate.Checked = false;
dtBirthDate.Value = DateTime.Today;
dtBirthDate.Checked = false;
}
// Can be used to Search 2 diff text field values.
private void LoadGrid()
{
string criteria = "StudentName like '%" +
txtSearchByName.Text + "%' AND RegNo like '%" + txtSearchByRegNo.Text +
"%' AND Status <> " + (Int16)eStatus.Deleted;
studentTable = StudentManager.GetStudents( criteria );
grdStudent.DataSource = studentTable;
}
74
LoadCurrentItem();
EnableFields( true );
SetEditState( true );
}
ClearFields();
EnableFields( true );
SetEditState( true );
}
if ( txtRegNo.Text == String.Empty )
{
MessageBox.Show ( "Please enter the Register
Number.", "Error", MessageBoxButtons.OK, MessageBoxIcon.Warning );
txtRegNo.Focus();
return;
}
Student student;
if ( pageAction== "ADD" )
{
// We are creating a new student.
student.Status = (int)eStatus.New;
}
else
{
// We are editing an existing student.
int id = int.Parse
( grdStudent[grdStudent.CurrentRowIndex, 0].ToString() );
student = StudentManager.GetStudent( id );
}
student.Homepage = txtHomepage.Text;
student.Email = txtEmail.Text;
student.Phone = txtPhone.Text;
student.StudentAddress = txtAddress.Text;
student.StudentName = txtName.Text;
student.AdmittedBy = txtAdmittedBy.Text;
student.PrevSchoolName = txtPrevSchool.Text;
student.ReasonForLeaving = txtReasonForLeaving.Text;
student.PrevSchoolPhone = txtPrevSchoolPhone.Text;
student.PrevSchoolAddress = txtPrevSchoolAddress.Text;
student.Remarks = txtRemarks.Text;
student.FatherName = txtFather.Text;
student.RegNo = txtRegNo.Text;
student.MotherName = txtMother.Text;
student.FatherOfficePhone = txtFatherOfficePhone.Text;
student.FatherCellPhone = txtFatherCellPhone.Text;
student.MotherResPhone = txtMotherOfficePhone.Text;
student.MotherCellPhone = txtMotherCellPhone.Text;
76
student.ResidencePhone = txtResPhone.Text;
student.ResidenceAddress = txtResidenceAddress.Text;
student.BatchId = (int)cmbBatch.SelectedValue;
student.LastModifiedTime = DateTime.Now;
student.AdmissionDateSelected =
dtAdmissionDate.Checked;
student.AdmissionDate = dtAdmissionDate.Value;
student.DateOfBirthSelected = dtBirthDate.Checked;
student.DateOfBirth = dtBirthDate.Value;
if ( pageAction== "ADD" )
{
int id = IdManager.GetNextID( "Student", "Id" );
student.Id = id;
StudentManager.CreateStudent( student );
}
else
{
StudentManager.UpdateStudent( student );
}
LoadGrid();
}
int id = int.Parse
( grdStudent[grdStudent.CurrentRowIndex, 0].ToString() );
Student student = StudentManager.GetStudent( id
);
student.Status = (int)eStatus.Deleted;
// Change status
StudentManager.UpdateStudent( student ); //
Update record.
}
LoadGrid();
EnableFields( false );
SetEditState( false );
}
}
}
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<ProjectView>ShowAllFiles</ProjectView>
</PropertyGroup>
</Project>
<configuration>
<appSettings>
<add key="dsn" value="Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=..\..\SMS.mdb"/>
</appSettings>
</configuration>
<configuration>
<appSettings>
<add key="dsn" value="Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=..\..\SMS.mdb"/>
</appSettings>
</configuration>
A fixed system of keywords that provide for all structured constructs date declaration
and modularity characteristics.
Date declaration facilities that should include both simple and complex data
structures.
Subprogram definition and calling techniques that support various nodes of interface
description.
CHAPTER 6
SCREEN SHOTS
80
Installation
The database as it is developed by SQL server 2005 can be installed only
by using the export and import concepts.
Using Dot Net and components like C# need proper deployment as per
general specifications developed the front end as it.
Main page:
Personal details:
81
Saved successfully:
82
Search:
85
Family:
86
Admission:
87
88
CHAPTER 7
Testing:
Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of software. The results of testing are used later
on during maintenance also.
Psychology of Testing
The aim of testing is often to demonstrate that a program works by showing that it has no
errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent of showing that a program
works, but the intent should be to show that a program doesn’t work. Testing is the
process of executing a program with the intent of finding errors.
Testing Objectives
The main objective of testing is to uncover a host of errors, systematically and with
A good test case is one that has a high probability of finding error, if it exists.
The software more or less confirms to the quality and reliable standards.
Acceptance
Testing
Client Needs
System Testing
Integration Testing
Unit Testing
6.2 Requirement:
System Testing:
The philosophy behind testing is to find errors. Test cases are devised with this in mind.
Code Testing:
This strategy examines the logic of the program. To follow this method we developed
some test data that resulted in executing every instruction in the program and module i.e.
every path is tested. Systems are not designed as entire nor are they tested as single
systems. To ensure that the coding is perfect two types of testing is performed or for that
91
matter is performed or that matter is performed or for that matter is performed on all
systems.
Types Of Testing
Unit Testing
Link Testing
Unit Testing
Unit testing focuses verification effort on the smallest unit of software i.e. the module.
Using the detailed design and the process specifications testing is done to uncover errors
within the boundary of the module. All modules must be successful in the unit test before
the start of the integration testing begins.
In this project each service can be thought of a module. There are so many modules like
Login, MasterAdmin, Normal User. Giving different sets of inputs has tested each
module. When developing the module as well as finishing the development so that each
module works without any error. The inputs are validated when accepting from the user.
In this application developer tests the programs up as system. Software units in a system
are the modules and routines that are assembled and integrated to form a specific
function. Unit testing is first done on modules, independent of one another to locate
errors. This enables to detect errors. Through this errors resulting from interaction
between modules initially avoided.
Link Testing
Link testing does not test software but rather the integration of each module in system.
The primary concern is the compatibility of each module. The Programmer tests where
modules are designed with different parameters, length, type etc.
Integration Testing
After the unit testing we have to perform integration testing. The goal here is to see if
modules can be integrated proprerly, the emphasis being on testing interfaces between
92
modules. This testing activity can be considered as testing the design and hence the
emphasis on testing module interactions.
In this project integrating all the modules forms the main system. When integrating all
the modules I have checked whether the integration effects working of any of the services
by giving different combinations of inputs with which the two services run perfectly
before Integration.
System Testing
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal os to see if software meets its requirements.
Here entire ‘ATM’ has been tested against requirements of project and it is checked
whether all requirements of project have been satisfied or not.
Acceptance Testing
Acceptance Test is performed with realistic data of the client to demonstrate that the
software is working satisfactorily. Testing here is focused on external behavior of the
system; the internal logic of program is not emphasized.
In this project ‘Network Management Of Database System’ I have collected some data
and tested whether project is working correctly or not.
Test cases should be selected so that the largest number of attributes of an equivalence
class is exercised at once. The testing phase is an important part of software development.
It is the process of finding errors and missing operations and also a complete verification
to determine whether the objectives are met and the user requirements are satisfied.
a statement level to find the maximum possible errors. I tested step wise every piece of
code, taking care that every statement in the code is executed at least once. The white box
I have generated a list of test cases, sample data. which is used to check all possible
combinations of execution paths through the code at every module level.
• Test cases that reduced by a count that is greater than one, the number of
additional test cases that much be designed to achieve reasonable testing.
• Test cases that tell us something about the presence or absence of classes
of errors, rather than an error associated only with the specific test at hand.
94
CHAPTER 8
CONCLUSION AND RECOMMENDATION
95
The entire project has been developed and deployed as per the requirements stated by the
user as student master, it is found to be bug free as per the testing standards that are
versions, which are planned to be developed in near future. The system at present does
not take care off the money payment methods, as the consolidated constructs need SSL
standards and are critically to be initiated in the first face, the application of the credit
card transactions is applied as a developmental phase in the coming days. The system
CHAPTER 9
BIBLOGRAPHY
97
Bi b l i o g r a p h y :