ASP.NET PROJECT

Authorized Learning Center (Code: - 1537)

College for Professional Studies

Opp. Maitidevi Temple, Kathmandu, Nepal

School Billing SYSTEM

SYNOPSIS of the PROJECT/PROJECT Draft

Madan Thapa

Roll No: 1502005563

BSCIT 6^th Semester

Sikkim Manipal University

Directorate of Distance Education

Jan, 2018

1. Title of the project

The title for this project is Pharmacy School Billing System. This project tries to find a very cozy solution for the School Management. This proposed application could be easily accessible by the general staffs of such accounts who have general knowledge of computer and this software will easily address the records of billing, restocking data, provides notification of low stock, and certainly it will reduce time and effort of user. Besides, through the implementation of this project, it would be very easy to find the reports on the daily/ weekly/ monthly/ yearly profits and the reports about them.

2. Project Introduction

The School Billing System is a real-time inventory database capable of connecting multiple users. The core concept is to track the billing of items from the cash registers with additional features for interpreting the data. This can provide the billing system systematically in the School Management. However, there are many numbers of student who are studying scholarship, some are with full payment etc. And all this thing cannot be record manually or might be difficult for billing for each student. Therefore, to run the School smoothly all the data should be record systematically in the computerized form. So that in the up coming future data can be retrieved easily.

In this System at first Admin user need to understand the setup part which helps to make familiar between the Billing System and School System. Therefore, admin user need to know all the School System then only He/She can setup the system in the Setup Part of the Billing System.

After Setting up the Setup part, Billing System will be ready to use by the other common user who can do billing only. And By only doing the billing our system gives the report of total collection daily or class wise.

Billing System is wide in use nowadays by many Schools and college. It makes the Management in the proper way or systematic way.

1 | P a g e

3. Existing System Overview

The existing system uses paper based manual system. The accounts relies on manual system has not been able to computerized its system. The document and information were obtained from Different School Accounts. Many Accounts is using manual system for performing all tasks like keeping records, pricing, storing billing records. All the information is recorded in ledger book and day book. This system cause’s chaos while retrieving information and generating information. The task of keeping records and processing transaction is time consuming and troublesome. There is no doubt that growing inventory cannot be managed by such a manual record and account keeping.

4. Statement of the problem

Information Technology (IT) had become inseparable part in any sector in order to cope with the present status. The manual system is accompanied with the hectic paper based scenario, so the need of abolishing the manual system is indeed necessary. The manual system used by the client has many drawbacks as explained by the client herself. Some of the drawbacks of the system are listed below:

The manual bookings implies to core chances of error especially during the time when the work pressure is high.

Manual paper work is somewhat hectic and sometimes creates chaotic scenario. Manually handling the tasks (keeping records, pricing, stock maintenance and

storing billing records) takes longer time than computerized system.

No adjustments can be carried out in the handheld paper documents once it’s done.

The report generation is less systematic and is generated partially with no acquired content.

Lack of data security in the manual, so any information can be easily obtained and modified.

Consumes longer time in order to add, search and modify records. Consumes longer time to obtain information.

2 | P a g e

5. Objectives

The objective of School Billing System is to manage the physical resources and their relationship, while ensuring that service level commitments are achieved. This process will:

Ensure efficient and timely identification of vital items that are being sold Assist in managing the accounts.

Provide a repository for asset protection The objectives of Billing Management are:

To identify and track all data processing assets in an Billing System Repository

To define the process by which assets are identified and maintained in the School Billing System

To provide Billing System access to all necessary personnel (data entry, view, update and deletion)

To provide a full range of reports that will satisfy informational requirements To document the School Billing System within the Standards and

Procedures Manual

To provide training to personnel responsible for supporting the School Billing System

6. Scope

Various scopes of the proposed project are:

Preparation of software that can replace current paper system to fully computerized system.

Easy to use interfaces will be used, so that anyone can use it without any difficulties.

Good option for accounts manager and owner to catch up on the current availability of stocks of items in the inventory.

3 | P a g e

7. Methodology

a. Feasibility Analysis

The proposed system is believed to help reduce the hardship encountered as previously only manual record keeping existed. The proposed system will give better documentation and record keeping for faster retrieval of data by multiple users. Developing and implementing a new system gives benefits by reducing workload, fast and automated calculations by the same human resources and the existing equipment. So, deploying the new system is considered to have operational, technical and economic feasibility. A feasibility analysis considers whether the proposed system will be cost-effective from a business point of view and whether it can be developed within existing budgetary constraints. It is the determination of the likelihood of success of the project. Four tests of feasibility are studied as follows:

i. Technical Feasibility

The Project is technically feasible. The nature of the language in which we are building the software is very supportive activities can be easily implemented. The defects can be easily reduced to a level matching the applications needs to a level matching the applications needs. The implementation is quite supportive.

ii. Operational Feasibility

Proposed projects are of course beneficial only if they can be turned into information systems that will ease the record keeping of administrative and financial records without adding much burden. Simply stated, this test of feasibility asks if the system will work when developed and installed. Are there major barriers to implementation?

iii. Economic Feasibility

This feasibility test is done to determine whether a system is economically acceptable. It determines whether the investment needed to implement the system will be recovered. It determines whether it is worthwhile to invest the money in the project or whether something else should be done with it.

4 | P a g e

iv. Legal Feasibility

It is perhaps the most powerful type of feasibility, but it is never formally in a system study document. This involves that extent of managerial support for changes to the present system. If “the boss” wants a new computer system, we can bet that it will be installed even if it is not technically, operationally, or economically feasible. Conversely, if the top executive does not want to install a new system, the most convincing reasons to have one will be ignored.

b. Software Development Methodology

To develop this software, I have used Iterative and Incremental Development Model. The iterative enhance model encounters the third limitation of the waterfall model and tries to combine a benefit of both prototyping and the waterfall model. The basic idea is that the software should be developed in increments, each increment adding some functional capability to the system unit the full system is implemented. At each step, extensions and design modifications can be made. Advantage of this approach is that it can result it better testing because testing each increment is likely to be easier than testing the entire system as in the waterfall model. The increment models provide feedback to the client i.e. useful for determining the final requirements of the system.

Fig: Proposed Methodology: Iterative and Incremental

5 | P a g e

c. Data collection

The data needed for this project is collected from “Charu School, Chabil Chowk, Kathmandu, Nepal”., where I personally visited and entered the manual details in the system.

d. Functional and Non-functional requirement specification Functional requirement of this projects are:

A functional requirement is a function or feature that must be included in any system to satisfy the needs and desires of the system to be developed and be acceptable to the users. Mainly the proposed system will include following things:

Administration

is able to register Staff and assign them username and password is be able to track of the billing in the accounts

is be able to maintain item is be able to add products categorically

is be able to receive notification of products depleting in stock

is be able to generate reports based on daily, monthly and yearly business is able to generate invoices

Staff

is be able to do Billing

is be able to receive notification of billing

is be able to generate reports based on daily, monthly and yearly business is able to generate invoices

At present, the manual system is used in all of the above specific tasks. The

matter of fact is the new system will make the job easier as well as less time consuming. On the other hand the use of technologies is inhabitable in present context to cope with the day to day changing scenario and work pressure.

Non-functional requirement of this projects are:

It is a description of the features, characteristics, and attributes of the system as well as any constraints that may limit the boundaries of the proposed solution.

i) Usability: This software has a web based GUI interface that gives the services on the click and is easier for the user to learn since the complexity can be

6 | P a g e

reduced by the modern tools of the dot net technology. This doesn’t require a person who is efficient in the computer.

ii) Reliability: The software is a prototype for the requirement and it cannot fulfill the requirements that are not dealt with but can be further extended according to the user’s requirement.

iii) Performance: The performance of the software is based on how much the admin and other regular staffs want to rely on the software for the operation of inventory.

iv) Supportability: Since the entire OOP is done in the Java technology which is taking the global market and the functions and classes are readily available as per requirement which makes it a reliable platform to use along with the required supports.

v) Scalability: This is a large scale program and the weight of the requirements can affect the performance.

vi) Extensibility: This system can be further extended to solve the problems that can occur or the problems that has not been identified currently. Moreover this application can be implemented for all sorts of large and small inventories.

7 | P a g e

8. Development

a. Proposed program flowchart

Fig: Proposed Program Flow Chart

8 | P a g e

. Proposed ER Diagram

10 | P a g e

11 | P a g e

d.		GANTT Chart

	S.	Task Complete	Total	Timeline in Days
	No		Days	5 7 14	39 42 56 60

1	Feasibility Study(System Analysis)	5

2	System Requirement Specification	2

3	Design (Database, Concept ,Function)	7

4	Programming Code	25

5	Testing	25 + 3

12 | P a g e

Documentation	14
Implementation	4

13 | P a g e

e. Proposed Program Modules

In this application, I have divided program under following modules.

i) Functions Module

This module contains logoff and password change facilities for all type of users. It also contains User Management section to be managed by the super user.

ii) Notification Module

This module is automated module. As soon as the items fall under user defined units, it will be shown on the main application panel until it is restocked. This is viewable by all users.

iii) User Management Module

This module is to be used by the admin, Admin will be allowed to the record of each users of the School Billing System while user will also be allowed to record billing.

iv) Inventory Module

This module is to be used by admin and staff. It contains inventory, items, suppliers, customer, category and invoice generation and printing.

v) Reports Module

This module is to be used by the admin and staff. admin can select report type and the date between which records are to be generated. Generating hard copy of the reports is also possible.

vi) Settings /Utilities Module

This module is to be used by the admin and staff. Staff can change his/her password only. Admin can change business information along with changing his/her password.

9. Hardware and Software to be used to develop the project

The requirements for this project are:

A. Hardware

a. CPU –PIV Processors

b. RAM – 2 GB

c. Hard Disk – 5GB

d. Keyboard, mouse, monitor

e. Printers

14 | P a g e

B. Software

a. Windows XP or higher or similar OS

b. Visual Studio 2012

c. RDBMS / Back end Tools: MySql 5.1

10. Backup and recovery

In School Billing System, there is a facility of backup of data. All the accounts data can be keep the backup for the uncertain accidental crash or loss of data.

When we lose our data, the only thing that will be important to us is our ability to restore the data and recover it quickly. It is important for individuals and businesses to understand the importance of backing up their data and implement data backup plans that require little to no human intervention.

It is critically important that data backup and recovery solutions are simple to implement, automated and that even the most novice computer user feels comfortable in retrieving data from backups if and when needed.

Backup helps to regain all the data and structure of the database in the predefined form which is most essential in every software in the daily work. As in the worst case scenario, anything can happen in the system or to the data. So we need to have the facility to go in back point or to gain the lost data from the system.

11. Testing Strategies

Testing is the means to identify the occurrence of any of these unwanted conditions and so prevent problems occurring. Testing should also purposely attempt to generate problems to determine the impact of errors. The testing phase is essential as software may contain bugs for many reasons, such as:

Software complexity.

Underestimation by programmers. Poorly documented code.

15 | P a g e

Changing requirements. Time pressures

Testing involves various strategies to be employed to successfully detect problems.

The various level of testing are explained as follows:

a) Unit testing

Unit testing is the lowest stage of testing. It occupies testing every module of a program in isolation. Unit testing is a micro scale of testing and involves the testing of particular functions or code modules. Normally it is carried out by the programmer and not by testers, as it necessitates detailed knowledge of the internal program design and code.

b) Integration testing

This is a test to see if the linkage between each tested module work correctly. Incremental integration testing involves continuous testing of an application as new functionality is added. It requires that various aspects of an application’s functionality be independent enough to work separately before all parts of the program are completed, or that test drivers are developed as needed. It is carried out by programmers or testers.

c) Acceptance testing

This is the process of comparing the program with its initial requirements specification and the current needs of its probable users. The description of this test is defined in the initial requirements and it includes the form, the quantity and the quality of what is to be delivered.

d) Installation testing

The main purpose of installation testing is to find the installation errors rather than software errors. When the program is installed, files or libraries are created, the hardware is configured. The program itself may have to interconnect with an operating system. As errors can occur during any of these operations, it is important to identify and correct them in advance.

Two methods of testing were performed in the software development.

a) White box testing

16 | P a g e

White-box testing (also known as clear box testing, glass box testing, transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application. In white-box testing an internal perspective of the system, as well as programming skills, are used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs. This is analogous to testing nodes in a circuit.

Using the White box testing the test cases can derive the following:

Guarantee that all independent paths within a module have been exercise at least once

Exercise all Logical decisions on their true or false sides Executes all loops at their Boundaries

Checks the internal data structure to ensure their validity

White box testing method includes following test case.

i) Condition testing

Condition testing is a test case design method that exercise the logical condition contained in a program modules.

ii) Data flow testing

Data flow testing methods selects test path of program according to the location of definition and uses of variables in the program. Data flow testing strategies are useful for selecting test paths of a program containing nested if and loop statement.

iii) Loop testing

Loop testing is a technique that focuses exclusively on the validity of loop construct. Four different classes of loops are

17 | P a g e

Simple loop Nested loop

Concatenated loop Unstructured loop

b) Black box testing

Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings.It typically comprises most if not all testing at higher levels, but can also dominate unit testing as well. In this testing Specific knowledge of the application's code/internal structure and programming knowledge in general is not required. The tester is only aware of what the software is supposed to do, but not how i.e. when he enters a certain input, he gets a certain output; without being aware of how the output was produced in the first place.

Black box testing attempts to find errors in the following categories:

incorrect or missing functions interface errors

errors in data structure or external database access Behavior or performance errors.

Initialization and termination errors

18 | P a g e

e) Snap Shot

Main Panel

Report

Code

Web.config

<?xml version="1.0"?>

<!--

For more information on how to configure your ASP.NET application, please visit

http://go.microsoft.com/fwlink/?LinkId=169433

-->

<system.web>

</system.web>

<add name="mycon" connectionString="server=DESKTOP-TA5O8PQ\MYSQLSERVER2008;database=major_project;integrated security=true;"

providerName="System.Data. SqlClient" />

<add name="major_projectConnectionString" connectionString="server=DESKTOP-TA5O8PQ\MYSQLSERVER2008;Initial Catalog=major_project;Persist Security Info=True;User ID=sa;Password=lbef"

providerName="System.Data.SqlClient" />

<add name="major_projectConnectionString1" connectionString="Data Source=DESKTOP-TA5O8PQ\MYSQLSERVER2008;Initial Catalog=major_project;Persist Security Info=True;User ID=sa;Password=lbef"

providerName="System.Data.SqlClient" />

</connectionStrings>

</configuration>

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Loginpage.aspx.cs" Inherits="Loginpage" %>

<!DOCTYPE html>

<title>WWW.Billing.com</title>

#form1 {

height: 234px;

width: 678px;

margin-left: 254px;

margin-top: 150px;

background-color:grey;

}

.auto-style1 {

width: 97%;

margin-left: 4px;

margin-top: 26px;

height: 40px;

}

.auto-style3 {

width: 243px;

}

.auto-style4 {

width: 243px;

height: 26px;

}

.auto-style5 {

height: 26px;

}

.auto-style6 {

width: 799px;

}

.auto-style7 {

width: 610px;

}

</style>

</head>

<legend>Login page </legend>

<tr>

<asp:Label ID="Label3" runat="server" Text="Label">Billing System</asp:Label>

</td>

</tr>

</table>

<tr>

<asp:Label ID="Label1" runat="server" Text="Username"></asp:Label>

</td>

<asp:TextBox ID="txtusername" runat="server" placeholder="username"></asp:TextBox>

</td>

</tr>

<tr>

<asp:Label ID="Label2" runat="server" Text="Password"></asp:Label>

</td>

<td>

<asp:TextBox ID="txtpassword" runat="server" placeholder="password" TextMode="Password">Password</asp:TextBox>

</td>

</tr>

<tr>

 </td>

<asp:Button ID="Button1" runat="server" Text="Login" style="margin-left: 109px" Width="56px" OnClick="Btnsubmit_Click" />

</td>

</tr>

</table>

<table>

<tr>

<asp:Label ID="Label_fail" runat="server" Text=""></asp:Label>

</td>

</tr>

</table>

<tr>

<asp:Label ID="label_footer" runat="server" Text="Copy@BillingSys"></asp:Label>

</td>

</tr>

</table>

</fieldset>

</div>

</form>

</body>

</html>

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Data.SqlClient;

using System.Data;

using System.Configuration; // this namespace is add I am adding connection name in web config file config connection name

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

{

protected void Page_Load(object sender, EventArgs e)

{

}

protected void Btnsubmit_Click(object sender, EventArgs e)

{

try

{

string uid = txtusername.Text;

string pass = txtpassword.Text;

SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["mycon"].ToString());

con.Open();

string qry = "select * from login where username='" + uid + "' and password='" + pass + "'";

SqlCommand cmd = new SqlCommand(qry, con);

SqlDataReader sdr = cmd.ExecuteReader();

if (sdr.Read())

{

Response.Redirect("Default.aspx");

}

else

{

Label_fail.Text = "UserId & Password Is not correct Try again..!!";

}

con.Close();

}

catch (Exception ex)

{

Response.Write(ex.Message);

}

Masterpage.aspx

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="MasterPage.master.cs" Inherits="MasterPage" %>

<!DOCTYPE html>

<style>

ul {

list-style-type: none;

margin: 0;

padding: 0;

overflow: hidden;

background-color: #333;

height: 47px;

}

li {

float: left;

width: 98px;

}

li a {

display: block;

color: white;

text-align: center;

padding: 14px 16px;

text-decoration: none;

}

li a:hover {

background-color: #111;

}

.auto-style1 {

width: 100%;

height: 929px;

}

.auto-style9 {

height: 32px;

}

.auto-style10 {

width: 1068px;

}

</style>

<asp:ContentPlaceHolder id="head" runat="server">

</asp:ContentPlaceHolder>

</head>

<tr>

<asp:Label ID="Label1" runat="server" Text="Billing System" Font-Size="XX-Large" ForeColor="White" Height="39px" Width="246px" style="margin-left: 433px"></asp:Label>

                 CURRENT YEAR:<asp:Label ID="Label_FiscalYear" runat="server"></asp:Label>

</td>

</tr>

</table>

<tr>

<td>

<ul>

<li><a href="#contact">Contact</a></li>

<li><a href="#contact">Gallery</a></li>

<li><a href="#about">About</a></li>

<li><a href="loginpage.aspx">logou</a></li>

</ul>

</td>

</tr>

</table>

<asp:ContentPlaceHolder id="ContentPlaceHolder1" runat="server">

<table>

<tr>

<asp:Label ID="SchoolName" runat="server"></asp:Label>

</td>

</tr>

</table>

</asp:ContentPlaceHolder>

<tr>

</tr>

</table>

</div>

</form>

</body>

</html>

Masterpage.aspx.cs

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Data.SqlClient;

using System.Data;

using System.Configuration;

public partial class MasterPage : System.Web.UI.MasterPage

{

protected void Page_Load(object sender, EventArgs e)

{

// Label_pass.Text = "Login Sucess......!!";

SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["mycon"].ToString());

con.Open();

SqlCommand cmd = new SqlCommand("Select * from setyear", con);

SqlDataReader dr;

dr = cmd.ExecuteReader();

while (dr.Read())

{

Label_FiscalYear.Text = dr["Batch"].ToString();

// SchoolName.Text = dr["SchoolName"].ToString();

}

dr.Close();

con.Close();

}

Registration.aspx

<%@ Page Title="" Language="C#" MasterPageFile="~/MasterPage.master" AutoEventWireup="true" CodeFile="Registration.aspx.cs" Inherits="Registration" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

.auto-style10 {

width: 100%;

height: 447px;

}

.auto-style11 {

width: 579px;

}

.auto-style12 {

width: 929px;

}

</style>

</asp:Content>

<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">

<table>

<tr>

<asp:Label ID="Label1" runat="server" Text="Admission Form"></asp:Label>

</td>

</tr>

</table>

</div>

<legend> Please Fill the Form</legend>

<tr>

<asp:Label ID="Label4" runat="server" Text="First Name"></asp:Label>

<asp:TextBox ID="Txt_fname" runat="server" style="margin-left: 109px" Height="26px"></asp:TextBox>

</td>

<td>

<asp:Label ID="Label5" runat="server" Text="Last Name"></asp:Label>

<asp:TextBox ID="txt_lname" runat="server" style="margin-left: 112px" Height="26px"></asp:TextBox>

</td>

</tr>

<tr>

<asp:Label ID="Label6" runat="server" Text="Class Room"></asp:Label>

<asp:DropDownList ID="DropDownList_Class" runat="server" DataSourceID="SqlDataSource_Class" DataTextField="Class" DataValueField="Classid">

</asp:DropDownList>

<asp:SqlDataSource ID="SqlDataSource_Class" runat="server" ConnectionString="<%$ ConnectionStrings:major_projectConnectionString %>" SelectCommand="SELECT [Classid], [Class] FROM [Class]"></asp:SqlDataSource>

</td>

<td>

<asp:Label ID="Label7" runat="server" Text="Roll No"></asp:Label>

<asp:TextBox ID="txt_rollno" runat="server" style="margin-left: 130px" Height="26px"></asp:TextBox>

</td>

</tr>

<tr>

<asp:Label ID="Label8" runat="server" Text="Gardian Name "></asp:Label>

<asp:TextBox ID="Txt_gardianname" runat="server" style="margin-left: 85px" Height="26px"></asp:TextBox>

</td>

<td>

<asp:Label ID="Label9" runat="server" Text="Gardian Number"></asp:Label>

<asp:TextBox ID="txt_gardiannumber" runat="server" style="margin-left: 76px" Height="26px"></asp:TextBox>

</td>

</tr>

<tr>

<asp:Label ID="Label10" runat="server" Text="Address"></asp:Label>

<asp:TextBox ID="txt_address" runat="server" style="margin-left: 125px" Height="26px"></asp:TextBox>

</td>

<td>

Blood Group                 <asp:DropDownList ID="DropDownList_Bloodgroup" runat="server" DataSourceID="SqlDataSource_Bloodgroup" DataTextField="Bloodgroup" DataValueField="Bloodgroupid">

</asp:DropDownList>

<asp:SqlDataSource ID="SqlDataSource_Bloodgroup" runat="server" ConnectionString="<%$ ConnectionStrings:major_projectConnectionString %>" SelectCommand="SELECT [Bloodgroupid], [Bloodgroup] FROM [Bloodgroup]"></asp:SqlDataSource>

</td>

</tr>

<tr>

<td>

Gender                                 <asp:ListBox ID="ListBox_gender" runat="server" Height="21px" Width="165px">

<asp:ListItem>Male</asp:ListItem>

<asp:ListItem>Female</asp:ListItem>

</asp:ListBox>

</td>

<td>

Batch                                    

<asp:DropDownList ID="DropDownList_Batch" runat="server" DataSourceID="SqlDataSource_Batch" DataTextField="Batch" DataValueField="Batchid">

</asp:DropDownList>

<asp:SqlDataSource ID="SqlDataSource_Batch" runat="server" ConnectionString="<%$ ConnectionStrings:major_projectConnectionString %>" SelectCommand="SELECT [Batchid], [Batch] FROM [Batch]"></asp:SqlDataSource>

</td>

</tr>

<tr>

<asp:Label ID="Label_Inserted" runat="server" Text=""></asp:Label>

<asp:Label ID="Label_fail" runat="server" Text=""></asp:Label>

</td>

<td>

<asp:Button ID="Button1" runat="server" Text="Save" style="margin-left: 240px" Width="74px" OnClick="Button1_Click" />

</td>

</tr>

</table>

</fieldset>

</asp:Content>

Registration.aspx.cs

using System;

using System.Collections.Generic;

using System.Linq;

using System.Web;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Data.SqlClient;

using System.Data;

using System.Configuration; // this namespace is add I am adding connection name in web config file config connection name

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

{

protected void Page_Load(object sender, EventArgs e)

{

}

protected void Button1_Click(object sender, EventArgs e)

{

SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["mycon"].ToString());

con.Open();

int Class = int.Parse(DropDownList_Class.Text);

int Bloodgroup = int.Parse(DropDownList_Bloodgroup.Text);

int Batch = int.Parse(DropDownList_Batch.Text);

string insert = "insert into studentmain (Fname,Lname,Classid,Rollno,Gardianname,Gardiannumber,Address,Bloodgroupid,Gender,Batchid) values ('" + Txt_fname.Text + "','" + txt_lname.Text + "','" + Class + "','" + txt_rollno.Text + "','" + Txt_gardianname.Text + "','" + txt_gardiannumber.Text + "','" + txt_address.Text + "','" + Bloodgroup + "','" + ListBox_gender.Text + "','"+Batch+"')";

SqlCommand cmd = new SqlCommand(insert,con);

int m = cmd.ExecuteNonQuery();

if(m != 0)

{

Label_Inserted.Text = "Student Admitted!";

Response.Redirect("Studentlist.aspx");

}

else

{

Label_fail.Text = "Student Not Admitted";

}

con.Close();

}

13.Conclusion

The problem constituted in the paper based and manual system is very huge. The desktop based “Pharmacy School Billing System” will help to resolve majority of the problems. But all problems may not be addressed. The manual existing system has lots of different issues that reduce the efficiency. The problems in the existing system can become the requirements for the new system. And it formed the basis for developing a new information system. This information system aimed to resolve the problem with the existing system

“Phamracy School Billing System” has been developed to fulfill all requirements of Mainly a School accounts and it will open a path of technology for all accounts managers. It provides computer based technology to accountss and thus help to increase quality of business and replace manual tasks of accounts administrative system.

Beautiful Music Mind

Sunday, September 23, 2018

ASP.NET PROJECT

0 comments:

Popular Posts

Join The Team

Facebook Like

Popular Posts