1.

INTRODUCTION
1.1 ABOUT THE PROJECT
The computer now comes to stay in everywhere and have proved to be
essential in the operations of business, production government, military, engineering
and researches.
Lot of modeling software now been developed and interactive computer
graphics enhances the power and value of the software.
Let us discuss about our topic in detail. This system we developed is to
maintain the Blood Bank Management System using Blood Bank. It includes
following tasks
onor !egister
"ollection !egister
#erology !egister
"ross $atching !egister
Issue !egister
Test !egister
Instrument !egister
Blood %roup !egister
Test !eport
"ollection !eport
Issue !eport
&
"omputeri'ations of these tasks are the main ob(ective of our Blood Bank
$anagement #ystem using Blood Bank. It is developed by using )isual Basic as
*ront+ ,nd Tool and $# -ccess as Back+,nd Tool.
.
. S!STEM STUD!
.1 E"ISTIN# S!STEM$
The ,/isting system in the Blood Bank Management is a manual system.
,ach and every action of registers is done manually using forms 0paper1. It takes more
time to finish and also having chances of committing some mistakes for each action.
The maintenance is also difficult for the e/isting system. -lso if the manual performs
the above re2uirements it takes more time to process.
DRA%BAC& O' E"ISTIN# S!STEM$
,very Thing is maintained in papers.
Time taken for each action is more.
)erification of data such as retrieved data, collected data,
etc are tedious
#everal tasks are to be maintained.
ue to these drawbacks of the e/isting system, there is a need for
computeri'ation.
3
. PROPOSED S!STEM$
In the proposed system, a software pack has developed to maintain all the
aspects of the e/isting system. The Tools, which we used here, are )I#4-L B-#I"
),!#I56 7.8 for the user interaction and $s+-ccess as atabase server.
The backend $# -ccess would store the soft copy details about the onors
!egister, "ollection !egister, #erology !egister, "ross $atching !egister, Issue
!egister, Test !egister, Instrument !egister and Blood %roup !egister. The system
will allow the user to modify, delete, and view any particular record without any
difficulties. The system should provide necessary security features to maintain the
records of officials. -ll the reports that we include are provided with necessary
information and are generated for managerial purpose.
'EATURES O' PROPOSED S!STEM
"ompletely menu+driven 9 used+friendly.
:rovides faster and efficient information processing.
#eparate tables are used to store separate information.
-dding, selecting, updating, editing can be easily done.
"omplete reports are attached to this pro(ect.
The main advantage is user friendly.
Thus the proposed system maintains a huge database, which records all the
details pertaining to customers and also keeps track of all the details which are
necessary for the organi'ation. The basis of the system lies in capturing and analy'ing
the information at various levels and effective decision making.
;
.( PROJECT DESCRIPTION
The e/isting was a very difficult one to entering the information about the
Blood Bank. But it the proposed system, it mainly reduce the man power and have a
very 2uick report for any details that related to the Blood Bank. -ll reports are trying
to do in )B data reports to get a 2uality reports.
<
(. S!STEM SPECI'ICATION
(.1 HARD%ARE SPECI'ICATION )MINIMUM1
:rocessor = i3
#peed = -bove <88 $>'
!-$ capacity = ;%B
*loppy disk drive = &.;; $B
>ard disk drive = <88 %B
$onitor = &?.< "olor $onitor
@eyboard = $ultimedia @eyboard
$ouse = 5ptical $ouse
(. SO'T%ARE SPECI'ICATION
5perating #ystem = $#+Aindows B:.
*ront ,nd = )I#4-L B-#I" 7.8.
Back ,nd = $# -ccess
MS ACCESS AN O*ER*IE%
$# -"",## is a powerful database management system and the user
can create application that re2uire little or no programming. It supports %4I
features and an entire programming language, )isual Basic -pplication which
can be used to develop richer and more developed application.
7
There are 2uite a few reasons, the first being that -ccess is a feature rich
program that can handle any database related task you have. Cou can create
places to store your data build tools that make it easy to read and modify your
database contents, and ask 2uestions of your data. -ccess is a relational
database, a database that stores information about related ob(ects. In $#
-"",## that database means a collection of tables that hold data. It
collectively stores all the other related ob(ects such as 2ueries, forms and
reports that are used to implement function effectively.
The $# -"",## database can act as a back end database for )isual Basic as a
front end, $# -"",## supports the user with its powerful database
management functions. - beginner can create hisDher own database very
simply by some mouse clicks. -nother good reason to use -ccess as backend
tool is that it is a component of the overwhelmingly popular $icrosoft office
software suite.
$# -"",## however is a relational database, which means that you
can define relationships among the data it contains. !elational database, are
superior to flat file databases because you can store discrete information.
- user can move inside table using the navigator tools supported by the
$# -"",## database. - table can be accessed in a number of ways like as a
#napshot, dynaset table etc., Because of these salient features in )isual Basic
and -ccess, I6I- choose )isual Basic as front end and -ccess as my Back
end.
?
O*ER*IE% O' *ISUA+ BASIC ,.-
$icrosoft visual basic is the newest version of the popular programming
Language. Aith its feature, visual basic is even stronger contender in the application
development area than ever before. It makes use of graphical user interface 0%4I1 for
creating robust and powerful application .%4I suggest use illustration to te/t, when
enable user to interact with an application. The feature makes it easier to comprehend
things in 2uicker and easier way.
"oding in %4I environment is 2uiet transition to traditional. Linear
programming methods when the user is guided through a linear path e/ecution and is
limited to a small set of operation. In %4I environment, the number of option open to
the user is much greater allowing more freedom to user and developers.
)isual basic was developed from basic programming language. In &E?8Fs
microsoft got its start by developing !5$ based interpreted B-#I" for early
microprocessor base computer.in&EG., microsoft Huick basic revolutioni'ed basic and
legitimi'e as serious development language for ms+dos environment.
$icrosoft "orporation created the enhanced version of basic called visual
basic for windows. It supports many useful tools that will help to be more productive.
These include but are not limited to, pro(ects forms, ob(ect templates, custom
controls, add+ins, and a database manager. ItFs specially designed to utili'e the
Internet. It comes several controls that allow to create web based application, called
active / e/ecutables. These will work (ust like the stand alone visual basic
applications they are accessed through the $icrosoft internet e/plorer web browser.
This allows to distribute the application through the internet.
G
In additional visual basic sports a new development environment, modeled
after the window e/plorer environment. This makes it easy for a computer user to
(ump right into creating application with visual basic.
'eat./es$
,asier comprehension.
4ser friendliness.
*aster application development.
Introduction to active / technology.
evelop robust stand+alone applications, games and utilities in less time
than it takes in other languages.
Interactive screen handling facilities.
)isual Basic is a Aindows programming language that has been developed at
$icrosoft "orporation. )isual Basic is a powerful programming language to develop
sophisticated windows programs very 2uickly. )isual Basic is one of this !- 0!apid
-pplication evelopment1 tool as it enables the programmer to develop applications
very easily and very 2uickly. It contains the same B-#I" like language that has been
popular over the years and it includes all this necessary e/tensions re2uired to
produce windows programs.
)isual Basic applications are very popular as front+end to many "lientDserver
database systems like #HLD#erver, 5racle etc.
E
*0s.al Bas01 Ed0t0ons$
)isual Basic software comes in three editions=
&. +ea/n0ng Ed0t0ons$ This includes the )isualBasic development environment and
use of standard tools to develop applications.
.. P/o2ess0onal Ed0t0on$ is used by computer professionals as it supports the tools to
develop -ctiveB and Internet controls.
3. Ente/3/0se Ed0t0on$ This includes all the features of professional edition as well
as $icrosoft )isual #ource safe for source code control and -utomation and
"omponent manager.
TEMP+ATES
Standa/d E"E$ "reate a stand+alone program that you can copy, give away, or
sell to others. ,/amples of stand+alone programs are $icrosoft Aord., Lotus &+.+
3, and 6etscape 6avigator. #tand+alone programs have a .,B, file e/tension.
A1t04e " D++$ "reates a file that has a .LL file e/tension. -ctive B LL files
are not meant to be used by them. Instead, these types of file contain subprograms
designed to be used as building blocks when creating a stand+alone program.
A1t04e " E"E$ "reates a file that has a .,B, file e/tension. 4nlike a stand+alone
,B, file, an -ctive B ,B, file is designed to work as an 5L, server, which is
nothing more than a program designed to share information with another program.
&8
A1t04e " Cont/ol$ "reates a file that has a .5"B file e/tension. 4nlike an
-ctiveB LL or -ctiveB ,B, file, an -ctive B "ontrol usually provides both
subprograms and a user interface that you can reuse in other programs.
A1t04e " Do1.ment D++$ "reates a file with a .LL file e/tension. -n -ctive B
document LL file is designed to help you run program on a web site.
A1t04e " Do1.ment E"E$ "reates a file that has as .,B, file e/tension. -n
-ctive B ocument ,B, file can display a )isual Basic form within an Internet
Aeb browser.
AddIn$ ,nables you to create an -ddIn program specially designed to work with
the )isual Basic user interface.
*B A33l01at0on %05a/d$ The )isual Basic friendly guide to help you create a
skeleton )isual Basic stand+alone ,B, program 2uickly and easily.
IIS A33l01at0on$ -n II# 0Internet Information #erver1 application is a )isual
Basic application that lives on a Aeb server and responds to re2uests from the
browser. -n II# application uses >T$L to present its user interface and uses
compiled )isual Basic code to process re2uests and responds to events in the
browser. II# applications can be used on the Internet or an Intranet. ,nd users of
an II# application do not need a specific operating system or browser. II#
applications use the -ctive #erver :age 0-#:1 ob(ect model.
DHTM+ A33l01at0on$ - >T$L 0ynamic >T$L1 application can also
respond to events in an >T$L page. >owever, >T$L applications are intended
for use on Intranets, and are dependent on Internet ,/plorer ;.8 or later. >T$L
applications use the ynamic >T$L ob(ect model.
&&
(.( DATABASE PRO#RAMMIN# %ITH *ISUA+ BASIC
ACTI*E" OBJECTS )ADO6
The -5 are used to access any datasource+relational databases, non
relational data sources, $icrosoft or any te/t file.
-5 accesses database data through an 5L,B provider. 5L,B which
cannot be accessed directly from visual basic.
The -5 data control
-ctiveB connection.
-ctiveB !ecord set.
&.
7. S!STEM ANA+!SIS
7.1 PROB+EM ANA+!SIS
The database developed for this system of linking the sections of Blood Bank
$anagement #ystem handles of large volume of data process it without an option of
deleting and maintains it.
The prime necessity of the system is it should accommodate data for Blood
transfers, "ertificate transfers etc. The also provide a confirmed security. ,/isting
system works are performed manually. Thus this should be rectified. ,ven though the
system may be computeri'ed it should be easy to use. The e/isting system takes more
process time. The reports are prepared manually. Thus the proposed system should
overcome these demerits.
7.'EASIBI+IT! STUD!
- feasibility study is conducted to select the best system that meets
performance re2uirements. This entities an identification description, an evaluation of
candidate systems, and the selection of the best system for the (ob.
Technical *easibility.
,conomical *easibility.
Behavioral *easibility
&3
TECHNICA+ 'EASIBI+IT!
The hardware, the software and to what e/tent they can support the proposed
system are the keys for this study. The Blood Bank has all the re2uired software
necessary for the system development.
ECONOMICA+ 'EASIBI+IT!
,conomical analysis is the most recently used method for evaluating
effectiveness of the proposed system. It has collo2uially known as cost benefits and
saving that are e/pected from the proposed system. 5therwise, further (ustification or
alterations in the proposed system will have to be made if it is to have a enhance to
approve.
BEHA*IORA+ 'EASIBI+IT!
-n ,stimate should be made of how strong a reaction the user staff is likely to
have towards the development of a computeri'ed system. It is common knowledge the
computer installation have something to do with blood transfers and employee (ob
status.
&;
8. S!STEM DESI#N
#ystem design is a solution,how to approach to the creation of the proposed
system. It provides the understanding and procedural detail necessary for
implementing the system recommended in the feasibility study. esign goes through
the logical and physical stages of development.
#ystem design includes
Input design
atabase design
5utput design
"ode design
ataflow diagram
PROCESS O' DESI#N
The design phase focuses on the detailed implementation of system
recommended in the feasibility study. ,mphasis is on translating performance
specification.
8.1 INPUT DESI#N
The input design process is to design the input needs into a machine+oriented
format. The ob(ect of input design is to create an input layout that is easy to follow
user friendly and to avoid operator errors.
&<
In accurate data cause most common errors in data processing made by data
entry operators. The help of error message can enter the re2uired and formatted date
by the user. #o you are design the inputted design to simply entered format.
The *ormatted input entries such as edit mask, radio button, drop down data
window help the user to enter the data very easily without much knowledge of the
product.
>ere also much care is taken to have standardi'ation over the %4I based
development with same standard set 9 rules.
The $enu based product helps even the native user work with the product.
The success are designs in such a way to help the user to get the information
whenever necessary.
8. DATABASE DESI#N
The most important consideration in designing the database is how
information will be used. The main ob(ectives of designing a database are=
Data 0nteg/at0on$
In a database, information from several file are coordinated, accessed and
operated upon as through it is in a single file. Logically, the information are
centrali'ed, physically, the data may be located on different devices, connected
through data communication facilities.
&7
Data 0nteg/0ty$
ata integrity means storing all data in one place only and how each
application to access it. This approach results in more consistent information, one
update being sufficient to achieve a new record status for all applications which use it.
This leads to less data redundancyI data items need not be duplicatedI a reduction in
the direct access storage re2uirement.
No/mal05at0on
In rational atabase design normali'ation is the process of organi'ing data and
minimi'e duplication. 6ormali'ation usually involves dividing a database into two or
more tables and defining relationship between the tables.
The ob(ective here is to isolate the data so that additions, deletions and
modifications of a field can be made one table and then propagated through the rest of
the database via the defined relationships.
6ormali'ation is to provide a fle/ible relational structure and maintain data
integrity.
T9e No/mal 'o/ms
6ormal forms are series of logical steps taken to normali'e data tables.
'0/st No/mal 'o/m$
In this all columns0fields1 must be atomic. It means no repeating items in
columns.
&?
Se1ond No/mal 'o/m$
!elational design is the second 6ormal form. 5nly when it is &6* and every
non+key column is fully dependent.
T90/d no/mal 2o/m$
*or a relationship design to be in 36* it has to be in .6* and every non+key
column has to be mutually independent.
8.( OUTPUT DESI#N
The 5utput designs are displayed some different report formats. ifferent
output design will improve the clarity and performing of output. The output designs
are classified into individuals and group of tables is possible.
-nd also display the reports are in lab tests, cross matching, issue details is
available in my pro(ect. It is used to check the collection of particular time of the
period.
8.7 CODE DESI#N
"oding style is manifest in the pattern of choices made among alternative
ways of e/pressing an algorithm. "onsistence coding style among difference
programmers enhances pro(ect communication and easily debugging testing, and
modification of the source code.
&G
#tandard and guidelines were discussed and several adherence to
programming guidelines under the proper conditions. $ost programmers will view
standard and guidelines as positive aspects of the work environment.
P/0n103les o2 1ode des0gn$
the need to communicate with and by means of, computers has made
increasing demands on uses to work with and understand computer codes instead of
natural languages.
Uniqueness: The code structure must ensure that only one value of the code with a
single meaning may be correctly applied to a given entity0or1 attribute, although that
entity0or1 attribute may be described by name in various ways.
Expansibility: The code structure must allow for growth of its set of entities0or1
attributes, thus providing sufficient space for the entry of new items within each
classification. The structure must also allow classification to be e/panded and others
added as re2uired.
&E
8.8 S!STEM '+O% DIA#RAM
.8
8., DATA '+O% DIA#RAM

'eat./es o2 Data 'lo: D0ag/am
&. The data flow diagram is logical because it represents the underlying
nature of whatFs actually happening in the system.
.. To perform one of ma(or functions+that of being an effective
communication medium with the user it must be completely free of
computer (argon.
3. It provides a starting point for structures design.
E;te/nal Ent0ty
-n ,/ternal ,ntity is a source 0or1 destination of data or both
for the system. It is represented as a double s2uare.
P/o1ess
:rocess transforms data from one form to, another by
performing some amount of work on the data.
.&
Data 'lo:
&. These represents the path over which data travels as it flows through the
system.
.. The data flows moving into and out of simple data stores do not re2uire
names.
3. 6o two data flows can have the same name.
;. The name given to a data flow must be meaningful as must be carefully
chosen to represents the data, which moves over it.
..
DATA '+O% DIA#RAM
.3
,. S!STEM TESTIN#<IMP+EMENTAION
-ll the modules of this system were successfully implemented and testing of
the pro(ect completed using test data as well as real data collected from the Blood
Bank. -ll the reports and the screens are tested for their validity and values in the data
tables are checked for their correctness and consistency. -fter successful testing of the
system, it was ready for implementation.
Types of testing
4nit testing
Integration testing
)alidation testing
#ecurity testing
,.1 UNIT TESTIN#
>ere the application is sliced into onors !egister, "ollection !egister,
#erology !egister, "ross $atching !egister, Issue !egister, Test !egister, Instrument
!egister and Blood %roup !egister. ,ach unit is tested individually.
.;
,. INTE#RATION TESTIN#
-fter unit testing, they are integrated into a single application and tested with
some sample data.
A11e3tan1e
-fter integrating, some units raise the errors and they are rectified. *inally the
application is accepted.
,.( *A+IDATION TESTIN#
-t the culmination of integration testing, software is assembled as a packageI
interface errors have been uncovered and corrected and a final series tests+validation
test begin. )alidation testing can be defined in any ways, but a simple definition is
that validation succeeds when the software functions in a manner that can be
reasonably e/pected by the customer. -fter validation test has been conducted, one of
two possible conditions e/ists.
The function or performanceFs characteristics conform to specification are
e/pected.
- derivation from specification is uncovered and a deficiency list is created.
,.7 SECURIT! TESTIN#
uring this testing, the tester plays the role of the individual who desires to
penetrate the system. The tester may also over when the system there by denying
service to others.
.<
,.8 S!STEM IMP+EMENTATION
- crucial phase in the system life cycle is the successful implementation of the
new candidate system design. Implementation simply means converting a new system
design into operational one. This involves creating compatible, training the operating
user, and installing the necessary hardware and terminals before the system is up
running.
Therefore implementation is the process of converting a new or revised system
design into an operational one. Thus during this stage the theoretical design is turned
into a working system. If the implementation stage is not carefully planned and
controlled, it can cause chaos. %enerally, there are three types of implementation as
follows
&. Implementation of a computer system to replace a manual system.
.. Implementation of a new computer system to replace an e/isting one.
3. Implementation of a modified application to replace the e/isting one using the
same e/isting system.
6ow this application is implemented on a new system and tested with the all
possible values, which gives the ma/imum performance.
.7
=. S!STEM MAINTENANCE
$aintenance of the system should be done accurately and with specific care
for the proper running of the system. $aintenance activity may re2uire the continuing
involvement of a large proportion of computer department resources. The main task
here is to adapt the e/isting system in the changing environment.
,/ternal design of the software involves conceiving planning out and
specifying the e/ternally observable characteristics of the software product. >ence the
system is design the way of easy maintenance.
The system is tested with various sample data, so the software has no chance
of errors. etailed design is concerned with the details of how to package the
processing modules and how to implement among modules and data structure.
Ahen the system maintenance it does not restart with the e/isting system as a
whole and then factor and degree of maintenance can improve with some change in
proposed system. The factor and degree of maintenance comes for the re2uirement
distillation of the program.
The system implementation involves various parts. ,ach part of the system
implementation is carefully analy'ed. >ence the runtime errors are avoided. The
modification of the code is also 2uite easy.
Thus maintenance is an important part in the system.
.?
>. CONC+USION
'.t./e S1o3e o2 t9e 3/o?e1t
The scale selection of data can be e/tended. The management details, the
blood e/piry details 9 >! details can be e/tended. #o that everything would be
computeri'ed.
The Blood Bank Management System in ,rode Blood Bank is validated and
sampled using wide spectra of inputs.
Ae have developed software for them and got opportunity to work in real time
environment. The system was tested by e/perts and found to be work very effectively.
It will be implemented very soon.
The pro(ect work is become success because of the following reasons.
The organi'ation can save money and the after implementing this
pro(ect.
$odification and maintenance can be made very easily since the
software is very much fle/ible.
)ery large data can be stored and also can be stored retrieved very
easily.
The software created is attractive and user+friendly. It is highly interactive too.
The software appears more fle/ible, which is completely menu+driven, it gives
advantage, as it needs less typing by the user.
.G
@. ENHANCEMENT
,nhancement refers to adding, modifying or redeveloping the code to support
changes in the specification. It is necessary to keep up with changing user
re2uirements and the operational environment.
6ormally application fail not because wear and tear but by eventually failing
to perform because of cumulative maintenance.
The system developed can be enhanced by the followings.
"ommerciali'ing the system
4pdating the database fre2uently
Boarding the search in due course of time etc
.E
1-. BIB+IO#RAPH!
&. 46L,-#>, )I#4-L B-#I" 7.8 0Techmedia1
+ !ob Thayer.
.. )I#4-L B-#I" 7.8 *5! %!546 4:
- %-!C "5!6,LL
3. )I#4-L B-#I" 7.8 I#T!IB4T, -::LI"-TI56
- $I">-,L L,,
- "L-!@ ">!I#T,6#
;. T,-"> C54!#,L* $I"!5#5*T -"",## .888
- ,C
- B4">-6-6
38
11. APPENDI"
11.1 TAB+ES
TAB+E NAME $ Blood#/o.3
:rimary @ey = Blood%rp
'0eld Name Data Ty3e S05e
Blood%rp "har <8
escription "har .<8
TAB+E NAME $ Colle1t0onReg
:rimary @ey = BagId
'0eld Name Data Ty3e S05e
BagId 6umber .
id 6umber .
5" ateDTime G
5, ateDTime G
6o5fBags 6umber .
BalanceBag 6umber .
3&
TAB+E NAME $ C/ossMat190ngReg
:rimary @ey = "$I
'0eld Name Data Ty3e S05e
"$I 6umber .
#erologyId 6umber .
onorId 6umber .
"$"ompatible Te/t .<8
TAB+E NAME $ Inst/.mentReg
:rimary @ey = InsId
'0eld Name Data Ty3e S05e
InsId 6umber .
Ins6ame Te/t <8
escription Te/t .<8
3.
TAB+E NAME $ Dono/Reg
:rimary @ey = id
'0eld Name Data Ty3e S05e
id 6umber .
onor6ame Te/t &88
*>6ame Te/t &88
%ender Te/t &
-ddress Te/t .<8
5ccupation Te/t &88
"ontact6o Te/t &<
$arital Te/t &8
Blood%roup Te/t &8
ob ateDTime G
Aeigh 6umber .
B: Te/t <8
%en-pp Te/t <8
Temperature Te/t <8
#killLesion Te/t <8
:ulse Te/t <8
!hType Te/t <8
!emarks Te/t <8
33
TAB+E NAME $ Iss.eReg
:rimary @ey = IssueI
'0eld Name Data Ty3e S05e
IssueI 6umber .
Iate ateDTime G
Bag6o 6umber .
#erology6o 6umber .
>ospital6ame Te/t <8
IssuedBy Te/t &88
6o5fBags 6umber .
TAB+E NAME $ Se/ologyReg
:rimary @ey = #id
'0eld Name Data Ty3e S05e
#Id 6umber .
:atient Te/t <8
5! ateDTime G
-ge 6umber .
!ef Te/t <8
>emoglobin Te/t <8
)!L Te/t <8
Blood%rp Te/t <8
!h*actor Te/t <8
>I) Te/t <8
>B Te/t <8
>") Te/t <8
>I)Aestern Te/t <8
3;
TAB+E NAME $ TestReg
:rimary @ey = LabId
'0eld Name Data Ty3e S05e
LabId 6umber .
Testate ateDTime G
:atient6ame Te/t <8
-ge 6umber .
!ef Te/t <8
>% Te/t <8
AB" Te/t <8
6uetra Te/t <8
Lympho Te/t <8
,#!& Te/t <8
,#!. Te/t <8
:lasma& Te/t <8
:lasma. Te/t <8
Aidal& Te/t <8
Aidal. Te/t <8
3<
11. SCREEN +A!OUTS
B+OOD BAN&MANA#EMENT S!STEMAERODE B+OOD BAN&
MAIN 'ORM
37
DONOR RE#ISTRATION
3?
CO++ECTION RE#ISTER
3G
SERO+O#! RE#ISTER
3E
CROSS MATCHIN# RE#ISTER
;8
ISSUE RE#ISTER
;&
TEST RE#ISTERAB+OOD TEST
;.
INSTRUMENT RE#ISTER
;3
B+OOD #ROUP RE#ISTER
;;
11.( REPORTS
REPORT 'ORM
;<
B+OOD TEST REPORT

;7
CO++ECTION REPORT

;?
ISSUE REPORT
;G
ISSUE RE#ISTER REPORT
;E
11.7 SAMP+E CODIN#
MAIN 'ORM
:rivate #ub "ommand&J"lick01
,nd
,nd #ub
:rivate #ub $I*ormJbl"lick01
,nd
,nd #ub
:rivate #ub $I*ormJLoad01
*ormTitle"aptions
$e."aption K :ro(ect6ame
*T."aption K $e."aption
*T.Left K 8
*T.Top K .;8
*T.Aidth K &.888
*T.Back#tyle K vbTransparent
*T.-lignment K vb"enter
*T.*ont#i'e K &<
*T.*ontBold K True
*T.*ore"olor K 9>;8G89
L4"on *T, $e."aption, $e, &&
Image&.Top K 8
Image&.Left K 8
Image&.Aidth K &.888
Image&.>eight K $e.>eight
Image&.:icture K Load:icture0Image6ames0811
Image&.#tretch K True
#et db K 5penatabase0-pp.:ath 9 MNataBase.mdbM1
L#et rs K db.5pen!ecordset0Mselect O from "ollection!egM1
,nd #ub
<8
:rivate #ub mnu&J"lick01
Load *orm&
*orm&.#how
,nd #ub
:rivate #ub mnu&&J"lick01
Load *orm&&
*orm&&.#how
,nd #ub
:rivate #ub mnu&.J"lick01
Load *orm&.
*orm&..#how
,nd #ub
:rivate #ub mnu&3J"lick01
LLoad *orm&3
L*orm&3.#how
$sgBo/ MLife of Bloods=+M 9 vb"rLf 9 M&. Ahole Blood + 3< days 0life1M 9 vb"rLf
9 J
M.. !B" + ;. daysM 9 vb"rLf 9 J
M3. **: + & year + *resh *ro'en :lasmaM 9 vb"rLf 9 J
M;. :latelet + < days + #plit from whole after centrifugeM, vbInformation P
vb5@5nly, :ro(ect6ame
,nd #ub
:rivate #ub mnu&;J"lick01
LLoad *orm&;
L*orm&;.#how
$sgBo/ MTotal "ount of Blood "ells M 9 vb"rLf 9 M&. >eamocytometerM 9 vb"rLf
9 M.. !ed Blood "ells 0,rythrocytes1M 9 vb"rLf 9 M3. Ahite Blood "ells
0Leucocytes1M, vbInformation P vb5@5nly, :ro(ect6ame
,nd #ub
<&
:rivate #ub mnu&<J"lick01
Load *orm&<
*orm&<.#how
,nd #ub
:rivate #ub mnu.J"lick01
Load *orm.
*orm..#how
,nd #ub
:rivate #ub mnu3J"lick01
Load *orm3
*orm3.#how
,nd #ub
:rivate #ub mnu;J"lick01
Load *orm;
*orm;.#how
,nd #ub
:rivate #ub mnu<J"lick01
Load *orm<
*orm<.#how
,nd #ub
:rivate #ub mnu7J"lick01
Load *orm7
*orm7.#how
,nd #ub
:rivate #ub mnu?J"lick01
Load *orm?
*orm?.#how
,nd #ub
:rivate #ub mnuGJ"lick01
Load *ormG
*ormG.#how
,nd #ub
:rivate #ub mnuEJ"lick01
<.
Load *ormE
*ormE.#how
,nd #ub
:rivate #ub mnu&8J"lick01
LLoad *orm&8
$sgBo/ M"entrifuge $achine M 9 vb"rLf 9 M&. >and "entrifuge K It reach upto
.888 to .<88 evolutions per minuteM 9 vb"rLf 9 M.. ,lectric "entrifuge K It reach
upto 3<88 r.p.mM, vbInformation P vb5@5nly, :ro(ect6ame
,nd #ub
:rivate #ub mnu"J"lick01
$I*orm&.-rrange vb"ascade
,nd #ub
:rivate #ub mnu,/itJ"lick01
,nd
,nd #ub
:rivate #ub mnu>J"lick01
$I*orm&.-rrange vb>ori'ontal
,nd #ub
:rivate #ub mnu)J"lick01
$I*orm&.-rrange vb)ertical
,nd #ub
:ublic #ub *ormTitle"aptions01
:ro(ect6ame K MBlood Bank$anagement #ystem + ,rode Blood BankM
*orm6ames081 K Monor !egisterM L*orm&
*orm6ames0&1 K M"ollection !egisterM L*orm.
*orm6ames0.1 K M#erology !egisterM L*orm3
*orm6ames031 K M"ross $atching !egisterM L*orm;
*orm6ames0;1 K MIssue !egisterM L*orm<
*orm6ames0<1 K MTest !eportM L*orm7
*orm6ames071 K M"ollection !egisterLs !eportM L*orm?
*orm6ames0?1 K MIssue !egisterLs !eportM L*ormG
<3
*orm6ames0G1 K MBlood %roup !egisterM L*ormE
*orm6ames0E1 K M"entrifuge $achineM L*orm&8
*orm6ames0&81 K MTest !egister + Blood TestM L*orm&&
*orm6ames0&&1 K MInstrument !egisterM L*orm&.
*orm6ames0&.1 K MLife of the BloodM L*orm&3
*orm6ames0&31 K MBlood "ellsM L*orm&;
L*orm6ames0&31 K MBalance :aymentM L*orm&;
L*orm6ames0&;1 K M"ustomer :ayment :endingM L*orm&<
Image6ames081 K -pp.:ath 9 MNpictureN3.(pgM L*orm&
Image6ames0&1 K -pp.:ath 9 MNpictureN3.(pgM L*orm.
Image6ames0.1 K -pp.:ath 9 MNpictureN3.(pgM L*orm3
Image6ames031 K -pp.:ath 9 MNpictureN3.(pgM L*orm;
Image6ames0;1 K -pp.:ath 9 MNpictureN3.(pgM L*orm<
Image6ames0<1 K -pp.:ath 9 MNpictureN3.(pgM L*orm7
Image6ames071 K -pp.:ath 9 MNpictureN3.(pgM L*orm?
Image6ames0?1 K -pp.:ath 9 MNpictureN3.(pgM L*ormG
Image6ames0G1 K -pp.:ath 9 MNpictureN3.(pgM L*ormE
Image6ames0E1 K -pp.:ath 9 MNpictureN3.(pgM L*orm&8
Image6ames0&81 K -pp.:ath 9 MNpictureN3.(pgM L*orm&&
Image6ames0&&1 K -pp.:ath 9 MNpictureN3.(pgM L*orm&.
Image6ames0&.1 K -pp.:ath 9 MNpictureN3.(pgM L*orm&.
Image6ames0&31 K -pp.:ath 9 MNpictureN3.(pgM L*orm&.
LImage6ames0&;1 K -pp.:ath 9 MNpictureN&E.(pgM L*orm&.
mnu&."aption K *orm6ames081
mnu.."aption K *orm6ames0&1
mnu3."aption K *orm6ames0.1
mnu;."aption K *orm6ames031
mnu<."aption K *orm6ames0;1
mnu7."aption K *orm6ames0<1
mnu?."aption K *orm6ames071
mnuG."aption K *orm6ames0?1
mnuE."aption K *orm6ames0G1
mnu&8."aption K *orm6ames0E1
<;
mnu&&."aption K *orm6ames0&81
mnu&.."aption K *orm6ames0&&1
mnu&3."aption K *orm6ames0&.1
mnu&;."aption K *orm6ames0&31
Lmnu&<."aption K *orm6ames0&;1
im ct -s Integer
Aith opt081
."aption K *orm6ames081
.Top K 8
.Left K 8
.Aidth K :icture..Aidth
.>eight K ;<8
.:icture K Load:icture0Image6ames0811
.*ontBold K True
.*ore"olor K *T.*ore"olor
.)isible K True
,nd Aith
im 5ptInd0&31 -s Integer
5ptInd081 K 8
5ptInd0&1 K &
5ptInd0.1 K .
5ptInd031 K 3
5ptInd0;1 K ;
5ptInd0<1 K &8
5ptInd071 K &&
5ptInd0?1 K G
5ptInd0G1 K <
5ptInd0E1 K 7
5ptInd0&81 K ?
5ptInd0&&1 K E
5ptInd0&.1 K &.
5ptInd0&31 K &3
*or ct K & To &3
Aith opt05ptInd0ct11
<<
."aption K *orm6ames05ptInd0ct11
.Top K opt05ptInd0ct + &11.Top P opt05ptInd0ct + &11.>eight
.Left K 8
.Aidth K :icture..Aidth
.>eight K ;<8
.:icture K Load:icture0Image6ames0811
.*ontBold K True
.*ore"olor K *T.*ore"olor
.)isible K True
,nd Aith
6e/t
,nd #ub
<7
DONORBS RE#ISTER
im !#tr01 -s #tring
:rivate #ub "ombo&J@eyown0@ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
"ombo..#et*ocus
,nd If
,nd #ub
:rivate #ub "ombo.J@eyown0@ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
5B.#et*ocus
,nd If
,nd #ub
:rivate #ub "ommand&J"lick01
im "hk -s Boolean
"hk K )alidation0$e1
If "hk K *alse Then
,/it #ub
,lse
im rs"ust -s !ecordset
#et rs"ust K db.5pen!ecordset0Mselect O from onor!eg where idKM 9
t/t081.Te/t1
If 6ot rs"ust.,5* Then
$sgBo/ Monor -lready ,/istsQM, vb"ritical, :ro(ect6ame
,/it #ub
,lse
im fn -s Integer
rs"ust.-dd6ew
*or fn K 8 To .
rs"ust0fn1 K t/t0fn1.Te/t
6e/t
<?
If 5ption&.)alue K True Then
rs"ust031 K 5ption&."aption
,lse
rs"ust031 K 5ption.."aption
,nd If
*or fn K 3 To <
rs"ust0fn P &1 K t/t0fn1.Te/t
6e/t
rs"ust0?1 K "ombo&.Te/t
rs"ust0G1 K "ombo..Te/t
rs"ust0E1 K 5B.)alue
*or fn K 7 To &3
rs"ust0fn P ;1 K t/t0fn1.Te/t
6e/t
rs"ust.4pdate
$sgBo/ M!ecord #tored #uccessfullyQM, vbInformation, :ro(ect6ame
"ommand.J"lick
"ommand3J"lick
,nd If
,nd If
,nd #ub
:rivate #ub "ommand.J"lick01
-ll"lear $e
t/t081.Te/t K I%enerates0MidM, Monor!egM1
t/t0&1.#et*ocus
"ommand7.Tag K MM
,nd #ub
:rivate #ub "ommand3J"lick01
L"ommand3.)isible K *alse
L"ommand;.)isible K True
im ">eads0&?1 -s #tring
">eads081 K Monor IdM
<G
">eads0&1 K Monor 6ameM
">eads0.1 K M*atherD>usband 6ameM
">eads031 K M%enderM
">eads0;1 K M-ddressM
">eads0<1 K M5ccupationM
">eads071 K M"ontact 6o.M
">eads0?1 K M$arital #tatusM
">eads0G1 K MBlood %roupM
">eads0E1 K Mate of BirthM
">eads0&81 K MAeightM
">eads0&&1 K MBlood :ressureM
">eads0&.1 K M%eneral -ppearenceM
">eads0&31 K MTemperatureM
">eads0&;1 K M#kin LesionM
">eads0&<1 K M:ulseM
">eads0&71 K M!h TypeM
">eads0&?1 K M!emarksM
Load$#* ">eads, $#*, Mselect O from onor!egM
,nd #ub
:rivate #ub "ommand;J"lick01
$#*."lear
$#*.)isible K *alse
L"ommand3.)isible K True
L"ommand;.)isible K *alse
,nd #ub
:rivate #ub "ommand<J"lick01
$e.>ide
,nd #ub
:rivate #ub "ommand7J"lick01
"ommand7.Tag K M,ditM
,nd #ub
<E
:rivate #ub "ommand?J"lick01
im "hk -s Boolean
"hk K )alidation0$e1
If "hk K *alse Then
,/it #ub
,lse
im rs"ust -s !ecordset
#et rs"ust K db.5pen!ecordset0Mselect O from onor!eg where idKM 9
t/t081.Te/t1
If rs"ust.,5* Then
$sgBo/ M6o onors -lready ,/istsQM, vb"ritical, :ro(ect6ame
,/it #ub
,lse
im fn -s Integer
rs"ust.,dit
*or fn K & To .
rs"ust0fn1 K t/t0fn1.Te/t
6e/t
If 5ption&.)alue K True Then
rs"ust031 K 5ption&."aption
,lse
rs"ust031 K 5ption.."aption
,nd If
*or fn K 3 To <
rs"ust0fn P &1 K t/t0fn1.Te/t
6e/t
rs"ust0?1 K "ombo&.Te/t
rs"ust0G1 K "ombo..Te/t
rs"ust0E1 K 5B.)alue
*or fn K 7 To &3
rs"ust0fn P ;1 K t/t0fn1.Te/t
6e/t
rs"ust.4pdate
78
$sgBo/ M!ecord 4pdated #uccessfullyQM, vbInformation, :ro(ect6ame
"ommand.J"lick
"ommand3J"lick
"ommand7.Tag K MM
,nd If
,nd If
,nd #ub
:rivate #ub 5BJ@eyown0@ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
t/t071.#et*ocus
,nd If
,nd #ub
:rivate #ub *ormJInitiali'e01
t/t0&1.#et*ocus
,nd #ub
:rivate #ub *ormJLoad01
$e."aption K *orm6ames081
4"on *T, $e."aption, $e, &
t/t081.Te/t K I%enerates0MidM, Monor!egM1
-dd"ombo
,nd #ub
:rivate #ub *ormJ!esi'e01
4"on *T, $e."aption, $e, &
,nd #ub
:rivate #ub $#*Jbl"lick01
im ( -s Integer
If "ommand7.Tag K M,ditM Then
*or ( K 8 To .
7&
t/t0(1.Te/t K $#*.Te/t$atri/0$#*.$ouse!ow, (1
6e/t
If $#*.Te/t$atri/0$#*.$ouse!ow, 31 K M$aleM Then
5ption&.)alue K True
,lse
5ption..)alue K True
,nd If
*or ( K 3 To <
t/t0(1.Te/t K $#*.Te/t$atri/0$#*.$ouse!ow, ( P &1
6e/t
"ombo&.Te/t K $#*.Te/t$atri/0$#*.$ouse!ow, ?1
"ombo..Te/t K $#*.Te/t$atri/0$#*.$ouse!ow, G1
5B.)alue K $#*.Te/t$atri/0$#*.$ouse!ow, E1
*or ( K 7 To &3
t/t0(1.Te/t K $#*.Te/t$atri/0$#*.$ouse!ow, ( P ;1
6e/t
t/t0&1.#et*ocus
,lse
$sgBo/ M"lick ,dit ButtonQM, vb"ritical, :ro(ect6ame
,nd If
,nd #ub
:rivate #ub 5ption&J@eyown0@ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
t/t031.#et*ocus
,nd If
,nd #ub
:rivate #ub 5ption.J@eyown0@ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
t/t031.#et*ocus
,nd If
,nd #ub
7.
:rivate #ub t/tJ@eyown0Inde/ -s Integer, @ey"ode -s Integer, #hift -s Integer1
If @ey"ode K &3 Then
If Inde/ K . Then
5ption&.#et*ocus
,lseIf Inde/ K < Then
"ombo&.#et*ocus
,lseIf Inde/ R t/t.4Bound Then
t/t0Inde/ P &1.#et*ocus
,lse
If "ommand7.Tag K M,ditM Then
"ommand?.#et*ocus
,lse
"ommand&.#et*ocus
,nd If
,nd If
,nd If
,nd #ub
:rivate #ub -dd"ombo01
Load"ombo "ombo., MBlood%roupM, MBloodgrpM
5B.)alue K 6ow
,nd #ub
CO++ECTIONS RE#ISTER
im !#tr01 -s #tring
:rivate #ub "ommand&J"lick01
im "hk -s Boolean
"hk K )alidation0$e1
If "hk K *alse Then
,/it #ub
,lse
im rs"ust -s !ecordset
#et rs"ust K db.5pen!ecordset0Mselect O from "ollection!eg where BagidKM 9
t/t081.Te/t1
73
If 6ot rs"ust.,5* Then
$sgBo/ M"ollections of this Bag 6o is -lready ,/istsQM, vb"ritical,
:ro(ect6ame
,/it #ub
,lse
im fn -s Integer
rs"ust.-dd6ew
rs"ust081 K t/t081.Te/t
rs"ust0&1 K t/t0&1.Te/t
rs"ust0.1 K 5".)alue
rs"ust031 K 5,.)alue
rs"ust0;1 K t/t0;1.Te/t
rs"ust.4pdate
$sgBo/ M!ecord #tored #uccessfullyQM, vbInformation, :ro(ect6ame
"ommand.J"lick
"ommand3J"lick
,nd If
,nd If
,nd #ub
:rivate #ub "ommand.J"lick01
-ll"lear $e
t/t081.Te/t K I%enerates0MBagidM, M"ollection!egM1
t/t0&1.#et*ocus
5".)alue K 6ow
5,.)alue K ate-dd0MdM, 3<, 6ow1
"ommand7.Tag K MM
,nd #ub
,nd
7;