Pro Inter

I I n nt tr ra an ne et t O Or rg ga an ni iz zi in ng g S Sy ys st te em m
R R. .V V. .S S c co ol ll le eg ge e o of f a ar rt ts s a an nd d s sc ci ie en nc ce e, , C Cb be e. .. . 1
INTRODUCTION

1.1 OVERVIEW OF PROJECT

This project entitled INTRANET ORGANIZING SYSTEM is proposed to
meet the requirements of the industry. Technology has become more important in all
aspects. Computers are one among them, which has rooted into the life style of the
humans.
Features of this project atomization of inter organizational activities of the
organization. This project can be transformation of Ups & Batteries and its
association, between head office and branch offices. The main advantages of this
project are the stock maintained separately from the head office and branch offices.

The areas taken to consideration are organization information, supplier details,
purchase management, branch management, order status management, dispatch
management, employee management, material requisition management, daily branch
report, etc.

This Project Consist of several modules like Branch office Module, Product Module,
Employee Module, Purchase Module, Stock Module, and Sales Module etc. we can
also take all the reports like monthly, date wise. Customized Reports are taken about
the modules involved in this project.

Project was developed with VB as front end and Microsoft Access as back end. Thats
all about the brief explanation of this project.

BRANCH OFFICE INFORMATION
It contain the information are branch code, branch name, branch in
charge name, branch street, branch city, branch pin code, branch fax no, branch email,
branch password, branch remarks.

PRODUCT INFORMATION
It contain the information are product code, product name, product
specification, product rate, product balance.

PURCHASE MASTER DETAILS
It contain the information are purchase order no, purchase order date, supplier code,
supplier in charge name, expected delivery date, mode, supplier balance amount,
purchase total amount, purchase sales tax, purchase net amount.
EMPLOYEE DETAILS
It contain the information are employee code, employee name, employee
designation, employee qualification, employee age, employee date of birth, employee
sex, employee street, employee city, employee phone no, employee email, employee
remarks.
PRODUCT CONFORMATION
It contain the information are product code, material requested no, material
requested date, branch code, branch in charge name, description, remarks.
BRANCH FINANCIAL DETAILS
It contain the information are finance code, finance date, branch code, total
expenses, average expenses, balance expenses, deposited bank, cash in hand.
It contain the information are branch code, branch name, branch inch
rage name, branch street, branch city, branch pin code, branch fax no, branch email,

1.2.2 STUDY OF EXISTING SYSTEM

Head office and branch office transaction is done in manually. Branch office
information is collected and maintained. Storing bulk of data manual leads to
problems. During search of fast information it leads manual work more and takes lot
of time. Manually maintaining information sometimes leads problems like lose of
information or mistakes in storing information.

EXISTING SYSTEM

Existing system is done manually.
The study of the existing system has thrown a light on various activities
involved in the organization and paved way for finding all requirements
needed.
The process is so tedious that the workers spend a good deal of their workers
spend a good deal of their time on it.
The potent for errors is great.
The basic function carried out is to have a note on the employee details, bus
details, trip details, trip cancellation, passenger details, and booking details.
Maintaining records of the employees manually is a very tedious process and
time consuming.
Calculating the payment of the trip manually is a very difficult task which
requires a lot of concentration and which is error prone.

2. SYSTEM ANALYSIS

2.1. STUDY OF PROPOSED SYSTEM
The existing system in the company is manual. The main disadvantages of
existing system,
Manual system is tedious.
It consumes more time.
Mistakes are committed.
Reports are more frequently needed.
Preparing reports all the time manually takes more times.

ADVANTAGES OF PROPOSED SYSTEM

The proposed system overcomes all the shortcoming and drawbacks of the
existing system.
Advantages of proposed system:
Security in databases.
Multiuse system.
Timesaving procedure.
Minimum numbers of files are used.
Any one with little knowledge of computer can handle the system.
The stock maintenance can handle separately in head office and branch
offices.
.

2.1.1 DEFINING THE PROBLEM

System Analysis is for finding out what happens in the existing system,
deciding on what changes and new features are required and defining exactly what the
proposed system must be. The process of system analysis is largely concerned with
determining, developing and agreeing to the users requirements. It provides prime
opportunity to communicate well with the user and conceive a joint understanding of
what a system should be doing, together with a view of the relative importance of the
system facilities using interactive techniques.
Initial investigation is the activity that determines whether the users
requisition is valid and feasible. The first step in initial investigation is the problem
definition. It includes the identification of the problem to be solved, the task to be
accomplished and the system goals to be achieved. Since the existing system is
manual the data processing and certain report generation may be time consuming.
Computerizing the system is an interactive; user-friendly layout can solve this
problem. The security of data in the manual system is less and providing a system that
holds administrative power via computerization it is the best remedial measure.
Fact-finding is an extremely important component of the communication process
which presents its own special set of problems and opportunities to people working to
increase the constructiveness of intractable conflicts. Facts are pieces of information
about the world that can be independently verified by generally accepted research
methods as reliable and a sound bases for decision-making and dispute resolution.
Facts may involve technical questions such as: the number of people living in a
particular area, number of acres of land under irrigation, the cost of constructing and
supplying a refugee camp, risks associated with a chemical plant, or the amount of
money that a company can afford to pay its employees and still remain competitive.
What exactly are the procedures for removing an elected official from office? Who
owns a particular piece of land? What are the legal rights that citizens have when
accused of a crime Thus the detail information about the problem defining.

2.1.2 DEVELOPING SOLUTION STRATEGIES

Detailed system study is a very critical activity while developing application
software. This phase involves detailed study of the existing system and interacting
with users to determine their requirements and specifications using certain techniques.
After the feasibility study, a detailed analysis of the existing system and the new
system is to be done.

It involves deep investigation of the existing system for collecting all data
carriers that are at present used in the organization. The formulae that are used for the
data carriers, forms, and records are thoroughly studied and limitations and
insufficiencies are stated. For overcoming these limitations and insufficiencies a new
system is proposed so that nature of the existing data manipulation may increase.

The main solution strategies in the Software scope describes the data and
control to be processed, function, performance, constraints, interfaces, and reliability.
Once scope has been identified (with the concurrence of the customer), it is
reasonable to ask: Can we build software to meet this scope? Is the project feasible?
All too often, software engineers rush part these questions, only to become mired in a
project that is doomed from the onset. Putnam and Myers address this issue as for
some projects in established areas the answers are easy.


2.2 SYSTEM SPECIFICATION

2.2.1 Hardware Specification:

The Hardware of the computer consist of physical components such as
input devices, storage devices, processing and control devices and output devices.
Computer includes external storage unit to store data in programs. The popular
external storage medium is Floppy disk, Compact disk etc,
The Hardware configurations involved in this project are:
.
Processor Intel Pentium IV
CPU Speed 240 MHz
RAM 256 MB
Hard Disk 40GB
VDU Intel (R) 8284 Graphics Controller
Disk Drive 1.44MB
Keyboard 104 keys
Mouse Logitech Scroll Mouse
2.2.2 Software Specification:

Software is a group of program that computers need to do a particular task. It
is an essential requirement of computer system.
The software is used to develop the project is Operating System.
Front End Microsoft Visual Studio
Back End Microsoft access
Connectivity ADO
FRONT END VB

In addition to hiding script commands, VB has the following advanced
features that help to develop robust web applications.

Compiled Code
Enriched Tool Support
Power and Flexibility
Simplicity
Manageability
Scalability
Security

Complied Code:
Code written is Compiled and not interpreted.
Application is faster to execute than other server side script that are interpreted

Enriched Tool Support:
The framework is provided with a rich toolbox and designer is IDE.

Power and Flexibility:
Applications are based on Common Language Runtime (CLR).
Therefore the power and flexibility of is available to application developers, is also a
language independent.

2.3 COST ESTIMATION AND SCHEDULING
Cost estimating is one of the most important steps in project management. A cost
estimate establishes the base line of the project cost at different stages of development
of the project. A cost estimate at a given stage of project development represents a
prediction provided by the customer.
Numerous computer aided cost estimation software systems are now available.
These range in sophistication from simple spreadsheet calculation software to
integrated systems involving design and price negotiation over the Internet. While this
software involves costs for purchase, maintenance, training and computer hardware,
some significant efficiency often result. In particular, cost estimates may be prepared
more rapidly and with less effort. Some of the common features of computer aided
cost estimation software include:
Databases for unit cost items such as salary of the employee and bus expenses.
These databases can be used for any cost estimate required. If these rates change, cost
estimates can be rapidly re-computed after the databases are updated. A typical
process for developing a cost estimate using one of these systems would include:
A cost estimate is calculated using the unit cost method of estimation. The cost
estimation is summarized and reviewed for any errors. A Successful project is that in
which the completed system is delivered on time and within the budget. There should
be no compromise on the quality what so ever. So realistic estimates of the time and
cost acquired in completing the project is critical to the project leader. Estimates are
carried out at various stages of a software project. As each stage, the reasons for
estimation for estimation and the methods used for estimation will be different

2.4 FINAL OUTLINE OF THE PROPOSED SYSTEM
Objectives of the proposed system:
The system objectives are to automate the important aspects of the system and to keep
track of the transaction status of the company. The system is designed in such a way
by giving prime importance of the following features.
Efficiency
Interactivity
Fully menu driven
User friendly
To reduce time of processing
Searching is kept to the administrators very easily.
Advantages of the proposed system:
The proposed system will reduce all the demerits of the existing system. The main
merits of the proposed system are:
The proposed system will reduce a lot of paper work there by saving time and
money. Managing of data that are stored in various tables is quietly easy.
Data redundancy is avoided to some extent.
A lot of errors that may occur during manual interaction can be avoided (i.e.,
high standard of accuracy can be maintained).
Storage of data can be done in a consistent manner.
Reports can be generated easily. Quick retrieval of information.
Provides user friendly entry screens to the end user as graphical user interface
based.

3. DESIGN AND DEVELOPMENT PROCESS
3.1 FUNDAMENTAL DESIGN CONCEPTS
System design is the next stage after the completion of the system study. In this stage
of system development, the processors are designed that are needed to convert the
input of the system into the output that achieves the systems goal.

Data Flow Diagram
The first step in system analysis is to draw a data flow diagram (DFD).
A DFD shows a logical flow of a system and defines the boundaries for the system.
A DFD, also known as a bubble chart has the purpose of clarifying
system requirements and identifying major transformation that will become programs
in system design.
A DFD consists of series of bubbles joined by lines. The bubbles
represent data transformation and the lines represent data flows in the system.
3.2 DFD symbols
A square defines a source or destination of system data.
An arrow identifies data flow data in motion. It is a pipeline through which
information flows.
A circle or a bubble represents a process that transforms incoming data flow
unto outgoing data flow.
An open rectangle is a data store-data at rest or a temporary repository of data.

3.2.1 DATAFLOW DIAGRAM

product information
Branch Office
information
Employee
Information

INTRANET
ORGANIZING
SYSTEM
ADMIN
Purchase Master
Information
New Order,
Order status,

Change password
complaints
Branch Product
Information
Branch Financial
Information
New product ,id
,brand,
quantity
Opening Stock
,
Purchase Rate,
Sale Rate, Current Stock
Employee Name, id Dept, DOJ
Salary etc Branch Name, Product Name,
No of quantity , Order status
Financial areas like debt, credit,
Opening balance , profit
DATAFLOW DIAGRAM
Level - 1

Employee
leave
details
Administrato
r
Employee_detail
s
Emp_det
Employee
attendanc
e
Emp atten_
Leave
approve
d
Employe
e salary
Emp_leav
e
Leave
approved
Emp_salary
Purchase
master
Purchas
e item
Purchase
transacti
on
Purchase
item
Produc
t infor
Produc
t stock
Product
conformatio
n
Purchase
trans
Product
stock
Product
confor
Supplier
infor
Supplier
order
Dispatch
Supplier
order
dispatch
Supplierinfro
Purchasemast
er
Purchase
trans

Level - 2

Branch
office
Branch
informati
on
Branchemp
det
Employ
ee
details
Branch
infor
Employ
ee
attenda
nce
Employ
ee
leave
Leave
status
Employe
e salary
branchEmpa
tten det
BranchEmp
leave
Branchemp
salary salary
branchLea
status
Produc
t infor
Branchproduct
infor
Produ
ct
stock
Register
s
reque
st
transact
ionn
Branc
h
finan
ce
Branch mat
req
Product
stock
Branchemp
det
Branchemp
det
Branch
finance
3.2.2 ER DIAGRAM
Level - 1

Emp_details
Emp_attendanc
e
Emp_code Empleave
details
Emp_salary
Emp_cod
e
Tot_work
Emp_da
Emp_oral
ll
Emp_p
f
Emp_esi
Emp_nsal Emp_hr
a
Tot_days
Emp_ode
de
Per_sal
Emp_basic
Tot_leave
Emp_cod
e
adate
Tot_days
Over_tim
e
Emp_cod
e
Tot_work
Lea_app
Emp_pre
Lea_avg
Lea_rem
Emp_rem
Emp_email
Emp_cod
e
Emp_nam
e
Emp_dob
Emp_se
x
Emp_phn
o
Emp_city
Emp_street
Emp_des
Emp_ag
e

Level - 2

Product_code
Product stock
Product conformation
Product
information
Purchase item
B_code
Mr_n
o
P_code
Bi_name
Mr_date
D_dis
rem
P_code
P_name
P_rate
P_spec
P_bal
P_code
P_bal
P_code
P_nam
e
P_qty
P_rate
Pm_cod
e
P_amt
Pt_code

Level - 3

Po_no
Supplier_information
Purchase master
S_code
Purchase transaction
Cur_amt
Che_bank
Che_amt
Cre_no
mpo
Si_name Che_dat
e
Che_no
Cre_amt
P_namt
Po_date
S_code
Cre_date
Sbal_amt
In_date
In_no
Cre_bonus
P_namt
P_saltax
P_totamt
Po_no
Po_dat
e
E_ddat
e
mod
e
Sbal-amt
S_code
Si_name
S_code
Si_name
S_name
S_street
S_pin
S_phno S_fno
S_email
spec
S_city
Sbal_amt
Level - 4

Branch_emple
ave
bemp_co
de
Tot_wor
k
bemp_
da
bemp_o
alll
bemp_
pf
bemp_
esi
bemp_n
sal
bemp_
hra
Tot_day
s
bemp_od
ede
Per_s
al
bemp_ba
sic
Branch emp
salary
bemp_co
de
App_
by
Time_re
q
Leareg_
no
Date_r
eq
Bemp_co
de
Date_fr
om
Lea_r
eq
Date_t
o
Branch_Empattend
ance
adat
e
Tot_day
s
Over_ti
me
bemp_co
de
Tot_wor
k
Lea_app
Emp_pr
e
Lea_av
a
Lea_re
m
Emp_details
bemp_r
em
bemp_em
ail
bemp_co
de
bemp_na
me
bemp_d
ob

p_dob
bemp_s
ex
bemp_ph
no
bemp_cit
y
bemp_str
eet
bemp_d
es
bemp_a
ge
Branchlea_st
atus
Bemp_co
de
status

Level - 5

Branch_sale
s
B_code
Branch_information
B_re
m
B_email
B_password
B_nam
e
B_code
B_stree
t
B_fno
B_phno B_pin B_city
Bi_name
Branch_mat_re
q
Mr_n
o
Mr_date
Mr_time
B_code
Req_perso
n
Branch_finance
fno
F_dat
e
B_code
T_exp
Dep_bank A_exp
Cash_hand
Dispatch
Sr_no
Sr_date
B_code
B1_sales
Bs_rem
Bs1_name
Bsales_ta
x
Bntax_turn
Btax_turn
Dc_no
Dc_dat
e
Ve_no
P_mod
B_code
Mr_n
o

Level - 6

P_code
Branch product_infor
Branch_product
stock
Branch registers
P_bal
P_rate P_spec P_name
P_code
P_code
P_name
P_stock
P_qty P_rate
P_code
P_bal
3.3 DESIGN PROCESS

The design process is an iterative process through which requirements are
translated into a blueprint for constructing the software. The design is represented at
a high level of abstraction. A level which can be directly traced to the specific system
objective and it can get more detailed data, functional and behavioral requirements.

Three characteristics that serve as a guide for the evaluation of a good design
The design must be implement all of explicit requirements contain in the
analysis model.
The design must be readable, understandable guide for those who generate
code and for those who test and subsequently support the software.
The design should provide a complete picture of the software, addressing the
data, functional, and behavioral domains from an implementation.

Basic design principles enable the software engineer to navigate the design
process
The design process should be traceable to the analysis model.
The design should be structured to accommodate change
The design should be structured to degrade gently, even when data, events or
operating conditions are encountered. Design is not coding, coding is not
design
The design should be assessed for quality as it is being created, not after the
fact.
The design should be reviewed to minimize conceptual error.
When these design principles are properly applied, the software engineer creates a
design that exhibits both external and internal quality factors.

3.3.1 DATABASE DESIGN

Database design is a crucial factor in the performance of a system both in terms of
system timing and in the case with which the system can be maintained or modified.

To permit simple retrieval of data in response to query and response request.

To simplify the maintenance of data through updates, insertions and deletions.

To reduce the need to restructure or reorganize data when new application
requirements arise.

The most important aspect of building an application package is database design. The
major steps involved in the database design are:

Identifying the data is needed for each table and their relationship.

Normalize the data.
Verify the design.
Implement the design.

If the database is completely normalized then the whole system becomes slow
because of various links. A compromise is done in certain aspects to increase the
response time. Hence some minimum amount of redundancy was allowed.

10. ANNEXURE
10.1 TABLE DESIGN

BRANCH EMPLOYEE ATTENDANCE
Primary key: Bemp_code
Field Data type Width Description
Bemp_code Varchar 5 Branch employee code
Adate Varchar 15 Date
Tot _work Int 4 Total working
Emp_pre Int 4 Employee present
Lea_app Int 4 Leave approved
Lea_ava Int 4 Leave available
Over_time Int 4 Overtime
Tot_days Int 4 Total days
Lea_rem Varchar 20 Leave remarks


BRANCH_EMPLOYEE DETAILS
Primary Key:bemp_code

Bemp_name Varchar 20 Branch employee name
Bemp_des Varchar 20 Branch employee designation
Bemp_qul Varchar 20 Branch employee
qualification
Bemp_age Int 4 Branch employee age
Bemp_dob Varchar 15 Branch employee date of
birth
Bemp_sex Char 1 Branch employee sex
Bemp_street Varchar 20 Branch employee street
Bemp_city Varchar 20 Branch employee city
Bemp_phno Varchar 20 Branch employee phone no
Bemp_email Varchar 20 Branch employee email id
Bemp_rem Varchar 20 Branch employee remarks


BRANCH EMPLOYEE LEAVE
Leareg_no Varchar 5 Leave register no
Date_req Varchar 15 Date request
Time_req Varchar 15 Time request
Lea_req Varchar 20 Leave request
Date_from Varchar 15 Date from
Date_to Varchar 15 Date to
App_by Varchar 20 Approved by

BRANCH EMPLOYEE SALARY
Foreign key:bemp_code
Bemp_code

Varchar 5 Branch employee code
Tot_work Int 4 Total work
Per_sal Int 4 Per day salary
Bemp_basic Int 4 Branch employee basic salary
Bemp_da Int 4 Branch employee disallowance
Bemp_hra Int 4 Branch employee hra
Bemp_oall Int 4 Branch employee overall
Bemp_pf Int 4 Branch employee pf
Bemp_esi Int 4 Branch employee ESI
Bemp_odet Int 4 Branch employee detection
Bemp_nsal Int 4 Branch employee net salary

BRANCH INFORMATION
Primary key:b_code
B_code Varchar 5 Branch code
B_name Varchar 20 Branch name
Bi_name Varchar 20 Branch in charge name
B_street Varchar 20 Branch street
B_city Varchar 10 Branch city
b-pin Int 4 Branch pin code
B_phno Varchar 20 Branch phone no
B_fno Varchar 16 Branch fax no
B_email Varchar 16 Branch email id
B_password Varchar 10 Branch password
B_rem Varchar 20 Branch remarks

BRANCH MATERIAL REQUEST
Foreign key:b_code
Mr_no Varchar 5 Material requisition no
Mr_date Varchar 15 Material requisition date
Mr_time Varchar 10 Material requisition time
Req_person Varchar 20 Requested person

BRANCH PRODUCT INFORMATION
Primary key:p_code
P_code Varchar 5 Product code
P_name Varchar 20 Product name
P_spec Varchar 20 Product specification
P_rate Int 4 Product rate
P_bal Int 4 Product balance

BRANCH PRODUCT STOCK
Foreign key:p_code

BRANCH REGISTERS
Foreign key:p_code
P_stock Int 4 Product stock
P_qty Int 4 Product quantity


BRANCH SALES
Foreign key:b_code
Sr_no Varchar 5 Sales request no
Sr_date Varchar 15 Sales request date
B1_sales Int 4 Branch 1 sales
Btax_turn Int 4 Branch tax turn
Btax_turn Int 4 Branch tax turn
Bsales_tax Int 4 Branch sales tax
Bs1_name Varchar 20 Branch sales name
Bs_rem Varchar 20 Branch sales remarks

BRANCH FINANCE
Foreign key:b_code
F_no Varchar 5 Finance no
F_date Varchar 10 Financial code
T_exp Int 4 Total expenses
A_exp Int 4 Average expenses
Dep_bank Int 4 Deposited bank
Cash_hand Int 4 Cash in hand

BRANCHLEAVE STATUS
Foreign key:bemp_code
Status Varchar 10 Status

DISPATCH
Foreign key:b_code
Dc_no Varchar 5 Dispatch no
Dc_date Varchar 15 Dispatch date
Mr_no Varchar 5 Material request no
P_mod Varchar 10 Payment mode
Ve_no Varchar 10 Vehicle no

EMPLOYEE ATTENDANCE
Foreign key:emp_code
Emp_code Varchar 5 Employee code
Adate Varchar 15 Attendance date
Emp_pre Int 4 Employee present
Lea_app Int 4 Leave approved
Lea_avg Int 4 Leave average
overtime Int 4 Overtime
Lea_rem Varchar 20 Leave remarks

EMPLOYEE DETAILS
Primary key:emp_code
Emp_name Varchar 20 Employee name
Emp_des Varchar 20 Employee designation
Emp_qul Varchar 20 Employee qualification
Emp_age Int 4 Employee age
Emp_dob Varchar 15 Employee date of birth
Emp_sex Int 4 Employee sex
Emp_street Varchar 20 Employee street
Emp_city Varchar 20 Employee city
Emp_phno Varchar 20 Employee phone no
Emp_email Varchar 20 Employee email
Emp_rem Varchar 20 Employee remarks

EMPLOYEE SALARY
Field Data type Width discription
Emp_code

Varchar 5 Employee code
Per_sal Int 4 Permanent salary
Emp_basic Int 4 Branch employee basic salary
Emp_da Int 4 Branch employee disallowance
Emp_hra Int 4 Branch employee hra
Emp_oall Int 4 Branch employee overall
Emp_pf Int 4 Branch employee pf
Emp_esi Int 4 Branch employee ESI
Emp_odet Int 4 Branch employee detection
Emp_nsal Int 4 Branch employee net salary

EMPLOYEE LEAVE DETAILS
Tot_leave Int 4 Total leave


LEAVE APPROVED

Lc_no Varchar 5 Leave conformation no
Lc_date Varchar 15 Leave conformation date
Leareg_no Varchar 5 Leave register no
Date_req Varchar 15 Date request
App_date Varchar 15 Approved date
App_by Varchar 20 Approved by
Status Varchar 20 Status

LOGIN
User_name Varchar 20 Username
Password Varchar 8 Password

Foreign key:p_code
Mr_no Varchar 5 Material request no
Mr_date Varchar 15 Material request date
Bi_name Varchar 20 Branch in charge name
D_dis Varchar 15 Description
Rem Varchar 20 Remarks

PRODUCT INFORMATION
Primary key:p_code
P_spec Varchar 20 Product specification

PRODUCT STOCK
Foreign key:p_code

PURCHASE ITEM
Foreign key:p_code
P_qty Int 4 Product quantity
P_amt Int 4 Product amount
Pm_code Varchar 5 Purchase material code
Pt_code Varchar 5 Purchase transaction code

PURCHASE MASTER
Po_no Varchar 5 Purchase order no
Po_date Varchar 15 Purchase order date
S_code Varchar 5 Supplier code
Si_name Varchar 20 Supplier in charge name
E_ddate Varchar 15 Date
Mode Varchar 10 Mode
Sbal_amt Int 4 Supplier balance amount
P_totamt Int 4 Purchase total amount
P_saltax Int 4 Purchase sales tax
P_namt Int 4 Purchase net amount

PURCHASE TRANSACTION
Foreign key:s_code
In_no Varchar 5 Invoice number
In_date Varchar 15 Invoice date
P_namt Int 4 Purchase net amount
mpo Varchar 26 More purchase order
Cre_no Int 4 Credit no
Cre_date Varchar 15 Credit date
Cre_bonus Varchar 20 Credit bonus
Cre_amt Int 4 Credit amount
Che_no int 4 Cheque no
Che_date varchar 15 Cheque date
Che_date varchar 20 Cheque bank
Che_amt int 4 Cheque amount
Cur_amt int 4 Current amount

SUPPLIER INFORMATION
Primary key:s_code
S_name Varchar 20 Supplier name
S_street Varchar 20 Supplier street
S_city Varchar 10 Supplier city
S_pin Int 4 Supplier pin code
S_phno Varchar 20 Supplier phone no
S_cellno Varchar 20 Supplier cell no
S_fno Varchar 20 Supplier fax no
S_email Varchar 20 Supplier emailid
Spec Varchar 20 Specification

SUPPLIER ORDER
Oa_no Varchar 5 Order accept no
Oa_date Varchar 15 Order accept date
Doa Varchar 15 Date of acceptance
Mode Varchar 20 Mode of dispatch

3.3.2 INPUT DESIGN

Input to a system can be defined, as the information is to be provided to the
system with this information it dose further in design making. Input design consists of
developing specification and procedures necessary for processing of input design is to
prevent the entry of invalid data.


PRODUCT INFORMATION

It contain the information are product code, material requested no,
material requested date, branch code, branch in charge name, description, remarks.

PURCHASE MASTER
It contain the information are purchase order no, purchase order date,
supplier code, supplier in charge name, expected delivery date, mode, supplier
balance amount, purchase total amount, purchase sales tax, purchase net amount.

EMPLOYEE DETAILS
It contain the information are employee code, employee name,
employee designation, employee qualification, employee age, employee date of birth,
employee sex, employee street, employee city, employee phone no, employee email,
employee remarks.

BRANCH EMPLOYEE DETAILS
remarks.


It contain the information are finance code, finance date, branch code,
total expenses, average expenses, balance expenses, deposited bank, cash in hand.

3.3.3 OUTPUT DESIGN

The output has designed in such a way that they present the same
format that they used. In the report layout the important items are highlighted, so that
they are able to find the fact. The report is designed in such a way that pages have a
title and a page number. It is also taken into care that the reports give the necessary
details and information that the report can readable.
The following are the outputs and reports that are generated from the
system.
Purchase master
Branch Product information
Product information
Product conformation
Branch information
Employee details
Branch employee details
Branch finance details
Branch stock details
PURCHASE MASTER DETAILS
It contain the information are purchase order no, purchase order date, supplier code,
supplier in charge name, expected delivery date, mode, supplier balance amount,
purchase total amount, purchase sales tax, purchase net amount.

EMPLOYEE DETAILS
remarks.

PRODUCT INFORMATION
It contain the information are product code, product name, product specification,
product rate, product balance.

It contain the information are product code, material requested no, material
requested date, branch code, branch in charge name, description, remarks.
BRANCH EMPLOYEE DETAILS
remarks.
It contain the information are product code, product name, product specification,
product rate, product balance.
It contain the information are finance code, finance date, branch code, total
expenses, average expenses, balance expenses, deposited bank, cash in hand.

BRANCH STOCK DETAILS
It contain the information are product code and product balance.

3.4 DEVELOPMENT APPROACH

Software scope describes the data and control to be processed, function,
performance, constraints, interfaces, and reliability.
Once scope has been identified (with the concurrence of the customer), it is
reasonable to ask: Can we build software to meet this scope? Is the project feasible?
All too often, software engineers rush part these questions, only to become mired in a
project that is doomed from the onset. Putnam and Myers address this issue as:
For some projects in established areas the answers are easy. You have done
projects like this one before. After a few hours or sometimes a few weeks of
investigation, you are sure you can do it again.
Projects on the margins of your experience are not so easy. A team may have
to spend several months discovering what the central, difficult to implement
requirements of a new application actually are. Do some of the requirements pose
risks that would make the project infeasible? Can these risks be overcome? The
feasibility team ought to carry initial architecture and design of the high risk
requirements to the point at which it can answer these questions. In some cases, when
the team gets negative answers, a reduction in requirements may be negotiated.
Meantime, senior managers are drumming their fingers nervously on their
large desks. Often, they wave their fat cigars in a lordly manner and yell impatiently
through the smoke screen,Enough do it! Many of the projects that appear in the
newspapers a few years later as whopping failures got started this way.
Putnam and Myers correctly suggest that scooping is not enough. Once scope is
understood, the software team and others must work to determine if it can be done
within the dimensions just noted. This is a crucial, although often overlooked, part of
the estimation process.
4. TESTING AND IMPLEMENTATION

4.1 SYSTEM TESTING
Software testing is a crucial element of software quality assurance and represents
the ultimate review of specification, design and coding. The increasing visibility of
software as a system element and the attendant "cost" associated with a software
failure are motivating forces for well-planned, thorough testing. Testing is a set of
activities that can be planned in advance and conducted systematically. Testing begins
at the module level and work towards the integration of entire computers based
system. Nothing is complete without testing, as it is vital success of the system.
Testing is an important stage in system development life cycle (SDLC).
Software testing is a critical element of software quality assurance and represents the
ultimate view of specification, design and coding.
Testing begins at the module level and work towards the integration of entire
computer based system. Nothing is complete without testing, as it is a vital success of
the system. There are three ways to test a program
For Correctness
For Implementation efficiency
For Computational Complexity
Tests for correctness are supposed to verify that a program does exactly what
it was supposed to do. This is much more difficult than it may first appear, especially
for large programs. Tests for implementation efficiency attempt to find ways to make
a correct program run faster and use less storage. It is a code refining process, which
re-examines the implementation phase of algorithm development.

4.1.1 TEST METHODOLOGIES AND POLICIES
Unit Testing
Unit testing focuses on the verification of smallest unit of software design of
the module. To check whether each module in the software works properly so that it
gives desired outputs to the given inputs. All validations and conditions are tested in
the module level in unit test. Control paths are tested to ensure the information
properly flows into and out of the program unit under test. Boundary condition are
tested to ensure that the modules operates at boundary establishes to restrict
processing. All independent paths through control structure are exercised to ensure
that all statements in a module have been executed at lease once. And finally all errors
handling paths are tested.

Black Box Testing
Black Box Testing methods focus on the functional requirements of the
software. This testing enables the software engineer to derive sets of input conditions
that will fully exercise all functional requirements for a program. This testing attempts
to find errors in the following categories: incorrect or missing functions, interface
errors, errors in data structure or external database access, performance errors and
initialization errors and termination errors
User Acceptance Testing
The performance of user interactive testing is actually the user show. The user
gives live data and checks whether software is giving specified outputs.

VALIDATION CHECKS:
Software validation is achieved through a series of black-box tests that
demonstrate conformity with requirements. A test plan outlines the classes of tests to
be conducted and a test procedure defines specific test cases that will be used to
demonstrate conformity with requirements. Both the plan and procedure are designed
to ensure that all functional requirements are satisfied, all behavioral characteristics
are achieved, all performance requirements are attained, documentation is correct, and
human engineered and other requirements are met.
After each validation test case has been conducted, one of two possible
conditions exists:
The function or performance characteristics conform to specification and are
accepted
A deviation from specification is uncovered and a deficiency list is created.
Deviation or error discovered at this stage in a project can rarely be corrected prior
to scheduled delivery. It is often necessary to negotiate with the customer to
establish a method for resolving deficiencies.

CONFIRGURATION REVIEW:
An important element of the validation process is a configuration review.
The intent of the review is to ensure that all elements of the software configuration
have been properly developed, are cataloged, and have the necessary detail to bolster
the support phase of the software life cycle.

ALPHA AND BETA TESTING:
When custom software is build for one customer, a series of acceptance tests
are conducted to enable the customer to validate all requirements. If software is
developed as a product to be used by many customers, it is impractical to perform
formal acceptance tests with each one. In that case alpha and beta testing can be done.

A customer conducts the alpha test at the developer's site by a customer. The
software is used in a natural setting with the developer "looking over the shoulder" of
the user and recording errors and usage problems. Alpha tests are conducted in a
controlled environment.

The beta test is conducted at one or more customer sites by the end -user of the
software. Unlike alpha testing, the developer is generally not present. Therefore, the
beta test is a "live" application of the software in an environment that cannot be
controlled by the developer.

TESTING METHODOLOGIES
The entire testing process can be divided into 3 phases
Unit Testing
Integrated Testing
Final/System Testing
Unit Testing As the system was totally GUI based, the following were tested
in this phase. Tab Order Field Length Menu Testing
Front end Validation
Unit testing focuses verification efforts on the smallest unit of software design
module. To check whether each module in the software works properly so that it gives
desired output to the given input.
The code modules were tested individually one after another. The following were
tested in each module.
Loop testing
Boundary value analysis
Control paths are tested to ensure the information properly flows into and out of the
program unit. Boundary conditions are tested to ensure that modules operate at
boundaries and restrict processing when gone beyond the set boundary. All
independent paths through the control structure ensure that the statements have been
executed at least once. Finally the error handling paths were tested.
In our testing the test data was given to each and every module in all respects and got
the desired results. Each module was found to be working properly.

Integration Testing
Integration testing is a systematic technique for constructing the program
structure, while conducting test to discover error associated with interfacing.
Integration test has been carried out successfully. The different modules of the system
were combined together to form an integrated working application.

Final/System Testing
This is the final step of testing. In this testing the entire system was tested as a whole.
This form of testing is known as Black Box Testing. Black Box testing enables us to
derive sets of input condition that will fully exercise all functional requirements for a
program. Black Box testing has been successfully carried out with test data and got
the desired output.

Test Data
Test data should be prepared carefully since data only determines the
efficiency and accuracy. All the above testing was successfully carried out for the
month of March 2003. The output given by the system agreed with test data output
created manually. Crosschecking has also been done with the existing System for
accuracy.

4.2 QUALITY ASSURANCE
Quality Assurance:
Quality assurance consists of the auditing and reporting functions of management.
The goal of assurance is to provide management with the data necessary to be
informed about product quality, thereby gaining insight and confidence that product
quality is meeting its goal.

Quality Assurance Goals
Correctness
The extent to which the program meets system specification and user objectives.

Reliability
The degree to which the system performs its intended functions over time.

Efficiency
The amount of computer resources required by a program to perform a function.

Usability
The effort required learning and operating a system.

Maintainability
To use with which program errors are located and corrected.

Testability
The effort required testing a program to ensure its correct performance.

Portability
The ease of transporting a program from one hardware configuration to another.

Accuracy
The required precision in input editing, computation and output.
4.2.1 GENERIC RISKS
A risk is a potential problem- it might happen, it might not. But, regardless of the
outcome, its really good idea to identify it, assess its probability of occurrence,
estimate its impact, and establish a contingency plan should the problem actually
occur.
The risk involves two characteristics

Uncertainty The risk may or may not happen; that is there are 100% problem
risks.
Loss - If the risk becomes a reality, unwanted consequences or losses will
occur.
Risk identification is a systematic attempt to specify threats to the project plan.

There are two types of risk
Generic risk This types of risks are a potential threat
Product specific risk It can be identified only by those with a clear
understanding of the technology, the people, and the environment that is specific
to the project at hand
The risk components are defined in the following manner:

Performance risk that the product will meet its requirements.
Cost risk that the project budget will be maintained
Support risk which the resultant project will be easy to correct , adapt, and
enhance
Schedule risk that the project schedule will be maintained and that the
product will be delivered on time.

4.2.2 Security Technology & Polices

Any system developed should be secured and protected against possible hazards.
Security measures are provided to prevent unauthorized access of the database at
various levels. At uninterrupted power will not erase the data in the files.

Password protection and simple procedures to change the unauthorized access are
provided to the users. The system allows the user to enter the system only through
login utility. The user will have to enter the user name and password.

4.3 SYSTEM IMPLEMENTATION
Implementation is the phase where the system goes for actual functioning.
Hence in this phase one has to be cautious because all the efforts undertaken during
the project will be fruitful only if the software is properly implemented according to
the plans made.
The implementation phase is less creative than system design. It is primarily
concerned with user training, site preparation and file conversion. Depending on the
nature of the system, extensive user training may be required. The initial parameters
of the MIS should be modified as the result of programming efforts; programming
provides a reality test for the assumptions made by the analyst.
The system testing checks the readiness and accuracy of the system to access
update and retrieve data from new files. Once the programs become available, the test
data are read into the computer and process.

Conversion means changing from one system to another. The objective is to
put the tested system into operation while holding costs, risks and personal irritation
to a minimum involves the following.
Creating Computer-Compatible Files
Training the operating staff
Installing terminals an Hardware

4.3.1 IMPLEMENTATION PROCEDURES
The system is developed in such a way that the existing facilities are enough
for implementation. The hard ware facilities are made sufficient enough to implement
the newly developed.
Implementation is the stage of the project. When the theoretical design is
turned into a working system. At this stage the main workload, the greatest upheaval
and the major. Impact in existing practices shift to user department. If the
implementation stage is not carefully, planed and controlled it can cause chaos. Thus,
it cant be considered to be the more crucial stage is achieving successful new stage
and in giving the user confidence that the system will work and be effective.

The implementation stage is a system project in its own right. It involves
careful planning, investigation of the current system and its constraints on
implementation, design of methods o achieve the change our procedures and
evaluation of change over methods.

The Implementation plan consists of the following steps

Testing the developed system with sample data.
Detection and correction of errors.
Making necessary changes in the system.
Checking the report with that of the existing system.
Training and involvement of user personnel.
Installation of Hardware and Software utilities.

The implementation of the system is easy for any system environment as the Software
is portable one.

4.3.2 USER TRAINING
An analysis of user training on two factors: user capabilities and the nature of
the system being installed. Developmental research provides interesting insights into
how computer users think about their first exposure to a new system.

Training Aids:

The user manual
The user manual is prepared reflexively because it is an item that must
accompany every system. A manual is necessary when the user is geographically
removed from the project team or when cannot attend all the training session. Of
course, if the user requests a manual, than one must be prepared.

Help Screens
This feature is now available in virtually every software package, especially
when it is used with a menu. Essentially, the user selects help option from a menu.
The system accesses the necessary description or information for user reference.

Data Dictionary
A data dictionary is a separate place for describing data elements.

Job aids
A job aid communicates essential information about certain jobs. It takes a number of
forms, for example:
a. Color Printing
b. Wall charts to illustrate schematics of processing runs.
Flowchart to guide the user in detecting and handling the errors
4.3.3 OPERATIONAL DOCUMENTATION
Documentation means of communication; a written record of a phase of a
specific project; it establishes design and performance criteria for phase of the project.
Documentation is descriptive information (e.g. Hardcopy manuals) that portrays the
use and / or operation of the system.

Documentation Tools
Document production and desktop publishing tool support nearly every aspect
of software developers. Most software development organizations spend a substantial
amount of time developing documents, and in many cases the documentation process
itself is quite inefficient. It is not use unusual for a software development organization
to spend as much as 20 or 30 percent of all software development effort on
documentation. For this reason, documentation tools provide an important opportunity
to improve productivity.

Document restructuring

Creating documentation is far too timed consuming. If the system works, well
live with what we have. In some cases, this is the correct approach. It is not
possible to recreate documentation for hundreds of computer program.
Documentation must be updated, but we have limited resources. Well use
document when touched approach. It may not be necessary to fully re-
document an application. Rather, those portions of the system that are
currently undergoing change are fully documented.
The System is business critical and must be fully re-documented. Even in this
case, an intelligent approach is to pare documentation to an essential
minimum.

4.4 SYSTEM MAINTENANCE

Provision must be made for environmental changes which may affect either
the computer or other parts of computerbased system. Such activity is normally
called maintenance. Responsibility for the maintenance of a particular system must be
allocated before any requirements for changes arise.
There is no need for separately qualified or trained or manual for operating the
system, because it has been developed in a user-friendly manner.

5. CONCLUSION

I have the project INTRANET ORGANIZING SYSTEM. This project
has been developed in VB. The datas are kept in MS. Access database and the project
is written in VB is used for validation and for data retrieval from the table. I have
done title; through there is scope for vast improvements and developments of our
project.

As for this project, it has been complete to our fullest satisfaction. I am also
confiding of fulfilling the future requirements as the need arises.

The new computerized system was found to be much faster and reliable and
user friendly then the existing system, the system has been designed and developed
step-by-step and tested successfully. It eliminates the human errors that are likely to
creep in the kind of working in which a bulk quantity of data and calculations has to
be processed.
The system results in quick retrieval of information that is very vital for the
progress any organization. Cost is minimized in case of stationary. Burden of manual
work is reduced as whenever transaction takes place, there is a no need to record it in
many places manually.
I once again express my sincere thanks to all those who lend me their helping
hand making this project a good success.

5.1 SCOPE FOR FURTHER ENHANCEMENT
Allowing about the various tourist requirements to view all the details about
the INTRANET ORGANIZING SYSTEM website elaborately can develop the
system further. They can also add extra details about company and advertiser in about
any new information they have developed. Giving the photo, click to display the all
information can further enhance the tourist website.

This project can also be developed in such a way if there are many branches in
a company the members or workers of the branch companies can poll their votes from
their own branch companies with the help of the online internet connection.

Every system should allow scope for further development or enhancement. The
system can be adapted for any further development. The system is so flexible to allow
any modification need for the further functioning of programs.

Since the objectives may be brought broad in future, the system can be easily
modified accordingly, as the system has been modularized. The future expansion can
be done in a concise manner in order to improve the efficiently of the system

5.2 BIBLIOGRAPHY:

1. BRETT TOMSON, JOE MARTIN, ASP. net
BPB Publications, 2001 Edition
2. D M DHAMDHERE. Systems Programming and Operating Systems.
Tata McGraw-Hill Publishing Company, II Edition, 2002.
3. ELIAS. M. AWAD, System Analysis and Design,
Galgotia Publications 1997 Edition.
4. JOYCE COX AND POLLY URBAN, MS Office for Windows 95
And Windows NT.
5. ROGER S.PRESSMAN. Software Engineering. Tata McGraw-Hill
Publishing Company, Vth Edition, 2001.
6. V S RAMASWAMY, S NAMAKUMARI, Marketing Management.
Published by Rajiv Beri for Macmillan India Ltd., 2
nd
Edition, 1995


ANNEXURE







CODING
Public Class WebForm39
Inherits System.Web.UI.Page

#Region Web Form Designer Generated Code

'This call is required by the Web Form Designer.
<System.Diagnostics.DebuggerStepThrough ()> Private Sub InitializeComponent
()
Me.SqlConnection1 = New System.Data.SqlClient.SqlConnection
Me.DataSet1 = New System.Data.DataSet
Me.SqlCommand1 = New System.Data.SqlClient.SqlCommand
Me.SqlDataAdapter1 = New System.Data.SqlClient.SqlDataAdapter
Me.SqlInsertCommand1 = New System.Data.SqlClient.SqlCommand
Me.SqlSelectCommand1 = New System.Data.SqlClient.SqlCommand
Me.SqlDataAdapter2 = New System.Data.SqlClient.SqlDataAdapter
Me.SqlInsertCommand2 = New System.Data.SqlClient.SqlCommand
Me.SqlSelectCommand2 = New System.Data.SqlClient.SqlCommand
Me.DataSet2 = New System.Data.DataSet
CType(Me.DataSet1, System.ComponentModel.ISupportInitialize).BeginInit()
CType(Me.DataSet2, System.ComponentModel.ISupportInitialize).BeginInit()
'
'SqlConnection1
'
Me.SqlConnection1.ConnectionString = "workstation id=M5;packet
size=4096;user id=sa;data source=m5;persist security inf" & _
"o=False;initial catalog=isabella"
'
'DataSet1
'
Me.DataSet1.DataSetName = "NewDataSet"
Me.DataSet1.Locale = New System.Globalization.CultureInfo("en-GB")
'
'SqlCommand1
'
Me.SqlCommand1.CommandText = "dbo.[bpinfo1]"
Me.SqlCommand1.CommandType =
System.Data.CommandType.StoredProcedure
Me.SqlCommand1.Connection = Me.SqlConnection1
Me.SqlCommand1.Parameters.Add(New
System.Data.SqlClient.SqlParameter("@RETURN_VALUE",
System.Data.SqlDbType.Int, 4, System.Data.ParameterDirection.ReturnValue, False,
CType(0, Byte), CType(0, Byte), "", System.Data.DataRowVersion.Current,
Nothing))
System.Data.SqlClient.SqlParameter("@p_code", System.Data.SqlDbType.VarChar,
5))
System.Data.SqlClient.SqlParameter("@p_name", System.Data.SqlDbType.VarChar,
20))
System.Data.SqlClient.SqlParameter("@p_spec", System.Data.SqlDbType.VarChar,
20))
System.Data.SqlClient.SqlParameter("@p_rate", System.Data.SqlDbType.Int, 4))
System.Data.SqlClient.SqlParameter("@p_bal", System.Data.SqlDbType.Int, 4))
'
'SqlCommand2
'
Nothing))
5))
20, System.Data.ParameterDirection.Output, False, CType(0, Byte), CType(0, Byte),
"", System.Data.DataRowVersion.Current, Nothing))
System.Data.SqlClient.SqlParameter("@p_rate", System.Data.SqlDbType.Int, 4,
System.Data.ParameterDirection.Output, False, CType(0, Byte), CType(0, Byte), "",
System.Data.DataRowVersion.Current, Nothing))
System.Data.SqlClient.SqlParameter("@p_bal", System.Data.SqlDbType.Int, 4,
'
'SqlCommand3
'
Nothing))
'
'SqlCommand4
'
Nothing))
5))
'
'SqlCommand5
'
Nothing))
5))
20))
20))
System.Data.SqlClient.SqlParameter("@p_rate", System.Data.SqlDbType.Int, 4))
'
'SqlDataAdapter1
'
Me.SqlDataAdapter1.InsertCommand = Me.SqlInsertCommand1
Me.SqlDataAdapter1.SelectCommand = Me.SqlSelectCommand1
Me.SqlDataAdapter1.TableMappings.AddRange(New
System.Data.Common.DataTableMapping() {New
System.Data.Common.DataTableMapping("Table", "branch_product_info", New
System.Data.Common.DataColumnMapping() {New
System.Data.Common.DataColumnMapping("p_code", "p_code"), New
System.Data.Common.DataColumnMapping("p_name", "p_name"), New
System.Data.Common.DataColumnMapping("p_spec", "p_spec"), New
System.Data.Common.DataColumnMapping("p_rate", "p_rate"), New
System.Data.Common.DataColumnMapping("p_bal", "p_bal")})})
'
'SqlInsertCommand1
'
Me.SqlInsertCommand1.CommandText = "INSERT INTO
branch_product_info(p_code, p_name, p_spec, p_rate, p_bal) VALUES (@p" & _
"_code, @p_name, @p_spec, @p_rate, @p_bal); SELECT p_code, p_name,
p_spec, p_rate" & _
", p_bal FROM branch_product_info"
Me.SqlInsertCommand1.Connection = Me.SqlConnection1
Me.SqlInsertCommand1.Parameters.Add(New
5, "p_code"))
20, "p_name"))
20, "p_spec"))
"p_rate"))
System.Data.SqlClient.SqlParameter("@p_bal", System.Data.SqlDbType.Int, 4,
"p_bal"))
'
'SqlSelectCommand1
'
Me.SqlSelectCommand1.CommandText = "SELECT p_code, p_name, p_spec,
p_rate, p_bal FROM branch_product_info"
Me.SqlSelectCommand1.Connection = Me.SqlConnection1
'
'SqlDataAdapter2
'
Me.SqlDataAdapter2.InsertCommand = Me.SqlInsertCommand2
Me.SqlDataAdapter2.SelectCommand = Me.SqlSelectCommand2
Me.SqlDataAdapter2.TableMappings.AddRange(New
System.Data.Common.DataTableMapping() {New
System.Data.Common.DataTableMapping("Table", "branch_product_info", New
System.Data.Common.DataColumnMapping() {New
System.Data.Common.DataColumnMapping("p_code", "p_code")})})
'
'SqlInsertCommand2
'
Me.SqlInsertCommand2.CommandText = "INSERT INTO
branch_product_info(p_code) VALUES (@p_code); SELECT p_code FROM bran"
& _
"ch_product_info"
Me.SqlInsertCommand2.Connection = Me.SqlConnection1
5, "p_code"))
'
'SqlSelectCommand2
'
Me.SqlSelectCommand2.CommandText = "SELECT p_code FROM
branch_product_info"
Me.SqlSelectCommand2.Connection = Me.SqlConnection1
'
'DataSet2
'
Me.DataSet2.DataSetName = "NewDataSet"
Me.DataSet2.Locale = New System.Globalization.CultureInfo("en-US")
CType(Me.DataSet1, System.ComponentModel.ISupportInitialize).EndInit()
CType(Me.DataSet2, System.ComponentModel.ISupportInitialize).EndInit()

End Sub
Protected WithEvents Label3 As System.Web.UI.WebControls.Label
Protected WithEvents pro_del As System.Web.UI.WebControls.Button
Protected WithEvents pro_add As System.Web.UI.WebControls.Button
Protected WithEvents pro_view As System.Web.UI.WebControls.Button
Protected WithEvents pro_mod As System.Web.UI.WebControls.Button
Protected WithEvents pro_exit As System.Web.UI.WebControls.Button
Protected WithEvents mp_bal As System.Web.UI.WebControls.TextBox
Protected WithEvents mp_spec As System.Web.UI.WebControls.TextBox
Protected WithEvents mp_name As System.Web.UI.WebControls.TextBox
Protected WithEvents mp_code As System.Web.UI.WebControls.TextBox
Protected WithEvents DropDownList1 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents SqlConnection1 As System.Data.SqlClient.SqlConnection
Protected WithEvents DataSet1 As System.Data.DataSet
Protected WithEvents SqlCommand1 As System.Data.SqlClient.SqlCommand
Protected WithEvents SqlDataAdapter1 As System.Data.SqlClient.SqlDataAdapter
Protected WithEvents mp_rate As System.Web.UI.WebControls.TextBox
Protected WithEvents TextBox1 As System.Web.UI.WebControls.TextBox
Protected WithEvents DropDownList2 As
System.Web.UI.WebControls.DropDownList
Protected WithEvents SqlDataAdapter2 As System.Data.SqlClient.SqlDataAdapter
Protected WithEvents SqlSelectCommand2 As
System.Data.SqlClient.SqlCommand
Protected WithEvents SqlInsertCommand2 As
Protected WithEvents DataSet2 As System.Data.DataSet
Protected WithEvents SqlSelectCommand1 As
Protected WithEvents SqlInsertCommand1 As

'NOTE: The following placeholder declaration is required by the Web Form
Designer.
'Do not delete or move it.
Private designerPlaceholderDeclaration As System.Object

Private Sub Page_Init(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Init
'CODEGEN: This method call is required by the Web Form Designer
'Do not modify it using the code editor.
InitializeComponent()
End Sub

#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
Dim i As Integer
Dim j As String
Dim k As String
Dim l As String
TextBox1.Text = Cache("b_code")

SqlConnection1.Open()
SqlDataAdapter2.Fill(DataSet2)
DropDownList2.DataSource = DataSet2
DropDownList2.DataTextField = "p_code"
DropDownList2.DataValueField = "p_code"
DropDownList2.DataBind()

i = DropDownList2.Items.Count()
If (i > 0) Then
DropDownList2.SelectedIndex = i - 1
j = DropDownList2.SelectedItem.Text
l = j.Length()
k = j.Substring(2, l - 2)
i = Val(k) + 1
k = "BP" + i.ToString
mp_code.Text = k
Else
mp_code.Text = "BP0"
End If
SqlConnection1.Close()

End Sub

Private Sub pro_add_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles pro_add.Click

SqlCommand1.Parameters("@p_code").Value = mp_code.Text
SqlCommand1.Parameters("@p_name").Value = mp_name.Text
SqlCommand1.Parameters("@p_spec").Value = mp_spec.Text
SqlCommand1.Parameters("@p_rate").Value = mp_rate.Text
SqlCommand1.Parameters("@p_bal").Value = mp_bal.Text
SqlCommand1.ExecuteNonQuery()

mp_name.Text = ""
mp_spec.Text = ""
mp_rate.Text = ""
mp_bal.Text = ""


Dim i = DropDownList2.Items.Count()
Dim j = DropDownList2.SelectedItem.Text
Dim l = j.Length()
Dim k = j.Substring(2, l - 2)
i = Val(k) + 1
mp_code.Text = k

End Sub

Private Sub pro_del_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles pro_del.Click


mp_name.Text = ""
mp_spec.Text = ""
mp_rate.Text = ""
mp_bal.Text = ""

mp_code.Visible = True
DropDownList1.Visible = False
pro_add.Enabled = True
pro_del.Enabled = False
pro_mod.Enabled = False


Dim l = j.Length()
i = Val(k) + 1
mp_code.Text = k

End Sub

Private Sub pro_view_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles pro_view.Click
DropDownList1.Visible = True
pro_del.Enabled = True
pro_mod.Enabled = True
pro_add.Enabled = False


End Sub

Private Sub pro_mod_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles pro_mod.Click
If mp_code.Text <> String.Empty Then
End If

DropDownList1.Visible = True
pro_add.Enabled = True
pro_del.Enabled = False
pro_mod.Enabled = False


Dim l = j.Length()
i = Val(k) + 1
mp_code.Text = k
End Sub

Private Sub pro_exit_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles pro_exit.Click
Response.Redirect("branch_module.aspx")
End Sub

Private Sub DropDownList1_SelectedIndexChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
DropDownList1.SelectedIndexChanged
SqlCommand2.Parameters("@p_code").Value =
DropDownList1.SelectedItem.Text
mp_code.Text = SqlCommand2.Parameters("@p_code").Value
mp_name.Text = SqlCommand2.Parameters("@p_name").Value
mp_spec.Text = SqlCommand2.Parameters("@p_spec").Value
mp_rate.Text = SqlCommand2.Parameters("@p_rate").Value
mp_bal.Text = SqlCommand2.Parameters("@p_bal").Value

End Sub
End Class

Pro Inter

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Pro Inter

Hochgeladen von

Copyright:

Verfügbare Formate

I I n nt tr ra an ne et t O Or rg ga an ni iz zi in ng g S Sy ys st te em m

Das könnte Ihnen auch gefallen