1. INTRODUCTION 1.1. ORGANIZATION PROFILE
This project is done in the garments named “GEETHA GARMENTS” which is loca locate ted d in Rakki Rakkiya yapal palay ayam am and star starte ted d rom rom !""!# !""!# The The manag managin ing g dire direct ctor or o the the company is Mr# Ashokk$mar# 1.2. ABOUT THE PROJECT
The “GARMENTS MANAGEMENT S%STEM” is to de&elop maintain the transactions perormed in a Garment 'ompany or a Shop in a easy manner (y the $se o men$s# )ith complete preca$tionary steps in maintaining the sec$rity o the system# The password prod$ction is $sed to a&oid the entry o $na$thori*ed $sers in the system#
+nce the access to the application has (een granted the $ser can contin$e with his work on the application selected, which is a &ery easy task as all mod$le ha&e (een designed with the common tool(ar#
Each mod$le has ($ttons attached (y which the set o coding has (een red$ced, which otherwise wo$ld ha&e (een a tedio$s process in designing has the same set o men$ (ar attached with its corresponding shortc$ts# The men$ designed to incl$de all the ollowing options where in each one pro&ides certain $nctions to (e carried o$t#
The end-$ser can take hard copy rom reports# . the comp$ter system has its printer, it is &ery easy to take hard copy o the data in the reports#
/
2. SYSTEM STUDY AND ANALYSIS 2.1. EXISTING SYSTEM
The E0isting system o the Garments is man$al system# Each and e&ery transaction o Garment is done man$ally in registers 1note2# .t takes more time an d some mistakes or each actions# The maintenance is also diic$lt or the e0isting system# .n the a(o&e re3$irements are perormed (y the man$al is &ery slowly# So we are introd$ced comp$ters or that work# DRAWBACK OF EXISTING SYSTEM:
E&ery thing is maintained in registers# Time taken or record the transactions in the register is more# 4eriication o data s$ch as retrie&ed data, collected data, etc are tedio$s# 5$e to these draw(acks or the e0isting system, there is a need or comp$teri*ation# 2.2. PROPOSED SYSTEM:
The e0isting system is a man$al process# The action is regarding system maintenance is recorded man$ally# .t is comp$teri*ed $sing 4.S6A7 8AS.' 4ERS.+N 9#"1:R+NT EN52 and Ms-Access ;#" 18A'< EN52# The (ackend Ms-Access sho$ld store the comp$ter details o data o =rod$cts, Employees and S$ppliers# That is like that =rod$ct No#, =rod$ct Name, >$ality 1E0port?7ocal2, S$pplier 5etails etc# Sho$ld allow the $ser to modiy, delete, and &iew any partic$lar record witho$t any diic$lties# The system sho$ld pro&ide necessary sec$rity eat$res to maintain the records oicials# All the reports sho$ld (e pro&ided with necessary inormation and are generated or managerial p$rpose#
+(jecti&e o the proposed system@ .ts easy to &iew a record whate&er we want at any cost in a 3$ick manner# To satisy all $ser re3$irements#
!
2. SYSTEM STUDY AND ANALYSIS 2.1. EXISTING SYSTEM
The E0isting system o the Garments is man$al system# Each and e&ery transaction o Garment is done man$ally in registers 1note2# .t takes more time an d some mistakes or each actions# The maintenance is also diic$lt or the e0isting system# .n the a(o&e re3$irements are perormed (y the man$al is &ery slowly# So we are introd$ced comp$ters or that work# DRAWBACK OF EXISTING SYSTEM:
E&ery thing is maintained in registers# Time taken or record the transactions in the register is more# 4eriication o data s$ch as retrie&ed data, collected data, etc are tedio$s# 5$e to these draw(acks or the e0isting system, there is a need or comp$teri*ation# 2.2. PROPOSED SYSTEM:
The e0isting system is a man$al process# The action is regarding system maintenance is recorded man$ally# .t is comp$teri*ed $sing 4.S6A7 8AS.' 4ERS.+N 9#"1:R+NT EN52 and Ms-Access ;#" 18A'< EN52# The (ackend Ms-Access sho$ld store the comp$ter details o data o =rod$cts, Employees and S$ppliers# That is like that =rod$ct No#, =rod$ct Name, >$ality 1E0port?7ocal2, S$pplier 5etails etc# Sho$ld allow the $ser to modiy, delete, and &iew any partic$lar record witho$t any diic$lties# The system sho$ld pro&ide necessary sec$rity eat$res to maintain the records oicials# All the reports sho$ld (e pro&ided with necessary inormation and are generated or managerial p$rpose#
+(jecti&e o the proposed system@ .ts easy to &iew a record whate&er we want at any cost in a 3$ick manner# To satisy all $ser re3$irements#
!
3. SYSTEM SPECIFICATION SPECIFICATION 3.1. SOFTWARE SPECIFICATION
:or a long time there were ew s$ch tools or de&eloping de&eloping )indows )indows appli applica cati tion on## 8eo 8eore re 4is$ 4is$al al 8asi 8asicc was was intr introd$ od$ce ced d in /BB/, /BB/, de&el de&elopi oping ng )ind )indow owss applica applicatio tions ns was m$ch m$ch harder harder that that de&elop de&eloping ing 5+S applica applicatio tions# ns# A 4is$al 4is$al 8asic 8asic dramatically changed the way people eel a(o$t and Microsot )indows# )ith 4is$al 8asic, programming or )indows has (ecome more eicient# 4is$al 8asic lets $s add men$s, te0t (o0es, command ($ttons, option ($ttons, check (o0es, scroll (ars and ile and directory (o0es to (lank )indows# )e can $se grids grids to handle handle ta($la ta($lator tor data, data, comm$n comm$nica icate te with with other other )indow )indowss application and access data(ase# . can ha&e m$ltiple windows on the screen# These windows ha&e $ll access to the clip(oard and to the inormation in most other )indows application r$nning at the same time# . can $se 4is$al 8asic to comm$nicate with other applications, which are r$nning $nder windows easily, $sing the most modern &ersion o Microsots +7E Technology#
C
VISUAL BASIC .! " A# $%&'%(&) 4is$al 8asic is o(ject Doriented i#e#, it re&ol&es aro$nd ready-made o(jects and it is e&ent Ddri&en, i#e#, all the acti&ities in a program are triggered (y one e&ent or another# Each o(ject also has its own e&ent handling#
The 4is$al 4is$al 8asic system system knows all a(o$t these already# already# .t knows how to handl handlee imag images es,, men$ men$ dial dialog og (o0es (o0es,, dri& dri&ee and and dire direct ctor ory y list list and and m$ch m$ch else else,, the the programmers jo( is to determine where, how and when an o(ject appears on the screen, what a is caption read and what happens when an e&ent occ$rs# The programmer doesnt ha&e to write code to trap these e&ents the system does it a$tomatically# +perations dont ha&e to ollow a set o se3$ence and can (e easily interr$pted or a(andoned# The process o program design relects the nat$re o the system# 4.S6A7 4.S6A7 8AS.' is the simplest simplest and earliest earliest - to D $se programmi programming ng lang$age or the windows en&ironment# .t has grown into with ar reaching capa(ilities and sophistication# The lang$age incl$des c$stom control elements like 'ommon 'ommon 5ialog 8o0, Grid, 5(grid, 5(com(o and 5(list# .t also incl$des +(ject 7inking Em(edding 1+7E2, 5ynamic 5ata E0change 155E2, 5ynamic 7ink 7i(raries 15772 and .nterace to the )indows )indows NT en&iron en&ironmen ment t it also also s$ppor s$pports ts +58' +58' and Str$ct Str$ct$re $red d >$ery >$ery 7ang$ag 7ang$agee 1S>72#
VISUAL BASIC *+ ,-& D&%&$/0, T$$ +(ject +riented Approach
+(ject oriented programming identiies the whole system as a collection o le0i(le entities called o(jects# The main task in this project is to identiy the o(jects in&ol&ed# 4is$al 8asic is o(ject oriented in a (road sense#
F
.t has a large n$m(er o ($ilt-in o(jects, which the $ser can $se with the ma0im$m le0i(ility# The only task or the programmer is to incorporate the ($ilt-in o(jects to his programs#
E%, D'(% P'$'*00(#
4is$al 8asic $ses e&ent-dri&en programming# +ne e&ent or the another triggers each acti&ity in the program# The core o 4is$al 8asic programming is a set o independent pieces o code that are acti&ated (y and so respond to only the e&ents they ha&e told to recogni*e# M$ch o the programming code e&ents s$ch as mo$se clicks occ$r in what 4is$al 8asic calls e&ents proced$re#
Essentially e&erything e0ec$ta(le in a 4is$al 8asic program is either in an e&ent proced$re to carryo$t its jo(# )rite the e&ent proced$res rom those e&ents and the s$(sidiary proced$res that make those e&ent proced$res work# )hen the application is r$nning, 4is$al 8asic monitors, the windows and the controls in each window or all the e&ents that each control can recogni*e mo$se moments, clicks, keystrokes and so on# )hen 4is$al 8asic e0amines the application to see i yo$ ha&e written an e&ent proced$re or that e&ent# 4is$al 8asic also pro&ides sophisticated error handling or all too common o pre&enting $sers rom (om(ing the application#
CONTROLS
'ontrols are the o(jects accessed rom Tool(o0# .t can (e pasted onto a orm and range rom ta(les which display te0t, thro$gh pict$re (o0es or graphic images, ($ttons, check (o0es, lists and men$s# Each control is associated with a set o properties#
TOOL BAR
=ro&ides 3$ick access to commonly $sed commands in the programming en&ironment, clicking on the tool (ar once wo$ld carry o$t the action#
PROCEDURE
All the codes in a program are written in proced$res or s$(ro$tines# All proced$res start with the keyword S68 and close with EN5S68#
FORM
The orm is the central $nit in 4is$al 8asic# .t is a window, initially (lank on which controls are pasted to create the re3$ired screen# Ser&es as )indows that can (e c$stomi*ed as the interace o an application# To create the look, controls, graphics and pict$res can (e added to the orm# Each orm is sa&ed on disk as a separate ile with a #:RM e0tension# MODULE
'ode that is attached to a orm is accessi(le rom anywhere on that orm# Howe&er the code that has to (e accessed rom a dierent orm, sho$ld (e written on a mod$le# The Mod$les are also sa&ed as separate iles, with #8AS e0tension#
PROJECT
The project holds together &ario$s orms and mod$les that make $p a program# .t is marked (y a #MA< e0tension#
MENU BAR
This is displayed on the top o the orm as ordinary men$ and code is written or each element o the men$# 8y clicking one item on the men$, corresponding code is e0ec$ted#
PROJECT WINDOWS
7ists the orm, code mod$les and c$stom control iles that make $p the c$rrent project# A project is a collection o iles $sed to ($ild an application# 9
PROPERTIES WINDOW
7ists the property settings or the selected rom or control# A property is the &al$e o an o(ject, s$ch as si*e, caption or color#
DATA TYPES
4is$al 8asic has ele&en data types# They are .nteger, 7ong, Single, 5o$(le, '$rrency, String, 8oolean, 8yte, 5ate and 4ariant#
DESIGN VIEW
To ($ild or modiy the str$ct$re o a orm, we work in orms design &iew# )e can add controls to the orms that are (o$nd to ields in a ta(le or 3$ery, incl$ding te0t (o0es, option ($ttons graphs and pict$res#
REPORT
A report is $sed to &iew and print inormation rom the data(ase# A report displays only the inormation we ant in the way we want to see it# The report can gro$p records into many le&els and comp$te totals and a&erage (y checking &al$es rom many records at once# Also the report is attracti&e and distincti&e (eca$se we ha&e control o&er the si*e and appearance o it#
MICROSOFT ACCESS .!AN OVERVIEW A data(ase is a collection o data# )ith Microsot Access we ($ild relational data(ase that store-related data in one place# Relational data(ases make it easier to ind, analy*e, maintain and protect the data, since the data is stored in only one place# A Microsot Access data(ase can contain si0 types o data(ase o(jects#
;
They are@ •
TA87E
•
>6ER%
•
:+RM
•
RE=+RT
•
MA'R+
•
M+567E
TABLE
A ta(le is a collection o data a(o$t a speciic topic# :or e0ample a ta(le can contain data a(o$t c$stomers or prod$cts# Ta(les organi*e data into col$mns 1called ields2 and rows 1called records2#
VIEW OF A TABLE
)e are work with a ta(le in two ways# 5esign 4iew 5atasheet 4iew
DESIGN VIEW
To ($ild or modiy the str$ct$re o a ta(le we work in a ta(les design &iew# )e can speciy what kind o data the ta(le will hold#
DATA SHEET VIEW
To add, edit or analy*e the data itsel we work in ta(les datasheet &iew mode#
4UERY A 3$ery is a 3$estion that has to (e asked a(o$t the data# :or e0ample which items are p$rchased rom a partic$lar &endor# Microsot Access gathers the data that answers the 3$estion rom one more ta(les# The data that make $p the answer is either dynaset 1i yo$ edit it2 or a snapshot 1i it cant (e edited2# Each time we r$n the 3$ery we get the latest inormation in the dynaset# Microsot Access either displays the dynaset or the snapshot or $s to &iew or perorm an action on it, s$ch as deleting or $pdating# VIEWS OF A 4UERY
5esign 4iew 5atasheet 4iew DESIGN VIEW
To ($ild or modiy the str$ct$re o a 3$ery we work in the 3$erys design &iew# This is where we ask 3$estions a(o$t o$r data to speciy what data we want and decide how data is to (e arranged# DATASHEET VIEW
To add, edit or analy*e the data itsel, i#e#, the data contained in the dynaset or record sets the answers or the 3$estions we ha&e posed, we work in 3$eries datasheet &iews# FORM
A orm is $sed to &iew and edit the inormation in the data(ase record (y record# A orm displays only the inormation we want to see in the way we want to see it# :orms $se the amiliar controls s$ch as te0t(o0es and check(o0es# This makes &iewing and entering data easy# )e ha&e control o&er the si*e and appearance o the orm#
VIEW OF A FORM
)e can work with orms in se&eral &iews# =rimarily there are two &iews
5esign 4iew
B
:orm 4iew
3.2. HARDWARE SPECIFICATIONS
+perating system
windows B
=rocessor
=enti$m !99-mm0
Ram
9F M8
Hard 5isk
/" G8
Speed
!99Mh*
'o- =rocessors
.n 8$ilt
Monitor
/F” S4GA
A$0illary Storage
/#FFM8, /#! M8
=rinter
7 I T /C! 'ol$mn 5ot Matri0 =rinter
3.3 SOFTWARE SPECIFICATION The conig$ration gi&en (elow is the sotware $sed or the system de&elopment
O/&'*,(# S5+,&0
@ Microsot )indows J= !"""
F'$#,
@ 4is$al 8asic 9#"
B*78
@ MS-A''ESS 1!"";2
/"
9. SYSTEM DESIGN 9.1 INPUT DESIGN .np$t design m$st (e in s$ch a way that it m$st control the amo$nt o inp$t, a&oid delay, etc# .t m$st (e simple# The inp$t design m$st ens$re $ser-riendly screen, with simplicity, pro&iding ease o &iewing I entering the data# E&ery inp$t data is &alidating# . the data is not &alid, proper error message are displayed#
The main o(jecti&e o designing inp$t oc$s on@ 'ontrolling the amo$nt o inp$t re3$ired# A&oiding delayed response# 'ontrolling errors#
Needless to say, thereore, that the inp$t data is the lie(lood o a system and ha&e to (e analy*ed and designed with at most case and consideration# The decisions made d$ring the inp$t design are To pro&ide cost eecti&e method o inp$t To achie&e the highest possi(le le&el o acc$racy To ens$re that inp$t is $nderstand (y the $ser# System analysis decide the ollowing inp$t design details like, wh at data to inp$t, what medi$m to $se, how the data sho$ld (e arranged or coded, data items and transaction needing &alidations to detect errors and at last the dialog$e to g$ide $ser in pro&iding inp$t#
//
.np$t data o a system may not (e necessarily is raw data capt$red in the system rom scratch# These can also (e the o$tp$t o another system or s$(system# The d esign o inp$t co&ers all phases o inp$t rom the creation o initial data to act$al entering the data to the system or processing# The design o inp$t in&ol&es identiying the data needed, speciying the characteristics o each data item, capt$ring I preparing data or comp$ter processing and ens$ring correctness o data#
.n this project, two main stages are presented s$ch as •
Main Men$ 5esign
•
:orm 5esign
MAIN MENU DESIGN .n this main men$ design, si0 types o men$s are presented here
M*+,&' •
S$pplier
•
'$stomer
•
5epartment
•
4ehicle
T'*#+*7,($# •
.npass
•
+$tpass
R&/$',+ •
S$pplier
•
'$stomer
•
5epartment
•
4ehicle /!
•
Type
•
.npass 5ate )ise
/C
9.2 OUTPUT DESIGN
+$tp$t 5esign generally reers to the res$lt and inormation that are generated (y the system or many end-$ser, o$tp$t is the main reason or de&eloping the system and the (asis on which they e&al$ate the $se$lness o the application#
The o(jecti&e o a system inds its shape in terms o the o$tp$t# The analysis o the o(jecti&e o a system leads to determination o o$tp$t# +$tp$t o a system can ace &ario$s orms# The most common are report, screen display, printed orms, graphical drawing etc#, the o$tp$t also &ary in terms o their contents re3$ency, timing I ormat# The $sers o the o$tp$t rom a system are the j$stiication or its e0istence# . the o$tp$ts are inade3$ate in any way, the system is the itsel is ade3$ate# The (asic re3$irement o o$tp$t are that it sho$ld (e acc$rate, timely and appropriate, in terms o co ntent, medi$m and layo$t or its intended p$rpose#
The o$tp$t design contains the ollowing reports@
=rod$ct Reports S$pplier Reports Employee Reports +rder?5eli&ery 'hallan Reports
)hen designing o$tp$t, system analysis most accomplish thing like, to d etermine what inormation to (e present, to decide whether to display or print the inormation and select and o$tp$t medi$m and to decide how to distri($te the o$tp$t to intended recipients#
E0ternal o$tp$t are those destination will (e o $tside the organi*ation and which re3$ire special attention as they project the image o the organi*ation#
/F
9.3. DATA BASE DESIGN NAME +: THE TA87E@ C,,(# FIELD NAME
TYPE
SIZE
CONSTRAINTS
DESCRIPTION
.5 '5ate
.nteger 5ate?Time
!
=rimary key Not n$ll
Emp id '$tting 5ate
EmpNo
.nteger
!
Not n$ll
Employee No
No=iece
.nteger
!
Not n$ll
>$antity
Rate
.nteger
!
N$ll
Rate
>$ality
Te0t
!
Not n$ll
>$ality
Type
Te0t
!
N$ll
Type
NAME +: THE TA87E@ E0/$5&&
FIELD NAME Empno Empname Address
TYPE .nteger Te0t Te0t
SIZE ! C"
CONSTRAINTS =rimary key Not n$ll
;
N$ll
'ity =hone 5+8 5+K >$ality E0p Salary Section
Te0t Te0t Te0t Te0t Te0t .nteger .nteger Te0t
C" / /" /" / ! ! /
Not n$ll Not n$ll N$ll Not n$ll N$ll N$ll N$ll N$ll
/
DESCRIPTION
Employee No Employee Name Employee Address 'ity =hone no 5ate o 8irth 5ate o Koin >$ality E0perience Salary Section
NAME +: THE TA87E@ O'6&' FIELD NAME +rNo
TYPE
SIZE
CONSTRAINTS
.nteger
!
=rimary key
DESCRIPTION +rder No
+r5ate
5ate
=.5
.nteger
!
Not n$ll N$ll
+rder 5ate =incode
S$pplier
Te0t
!
Not n$ll
S$pplier
7a(els
.nteger
Metres
.nteger
! !
Not n$ll N$ll
No#o#7a(els No#o#Metres
Si*e
Te0t
!
Not n$ll
Si*e
=ackage
Te0t
C
Not n$ll
=ackage
SIZE
CONSTRAINTS
NAME +: THE TA87E@ P'$67,
FIELD NAME =.5
.nteger
!
=rimary key
=ackage .d
=name
Te0t
Type >$ality
Te0t Te0t
" !
Not n$ll N$ll
=ackage Name Type
9
Not n$ll
>$ality
TYPE
DESCRIPTION
NAE +: THE TA87E@ P'7-*+&
FIELD NAME
TYPE
SIZE
CONSTRAINTS
DESCRIPTION
=date
5ate
=rimary key
=ackage 5ate
8illNo
.nteger
!
Not n$ll
8ill no
Rate
'$rrency
N$ll
Rate
>ty
.nteger
!
Not n$ll
>$antity
/9
NAME +: THE TA87E@ S,(7-(# FIELD NAME
TYPE
SIZE
CONSTRAINTS
DESCRIPTION
'.5
.nteger
!
=rimary key
'$tting id
'date
5ate
Not n$ll
'$tting 5ate
'$t.5
.nteger
!
N$ll
'$tting .d
EmpNo
.nteger
!
Not n$ll
Employee No
No=iece
.nteger
!
N$ll
No#o #=rice
Rate
.nteger
!
Not n$ll
Rate
NAME +: THE TA87E@ S//(&' FIELD NAME
TYPE
SIZE
CONSTRAINTS DESCRIPTION
S$pNo
7ong
F
=rimary key
S$pplier No
Name
Te0t
"
Not n$ll
S$pplier 5ate
Address
Te0t
/""
N$ll
Address
=incode
7ong
F
Not n$ll
=in 'ode
'ity
Te0t
"
Not n$ll
'ity Name
=hone
Te0t
C"
N$ll
=hone No
Mphone
Te0t
C"
Not n$ll
Mo(ile No
SIZE
CONSTRAINTS DESCRIPTION
NAME +: THE TA87E@ W*&+ FIELD NAME
TYPE
)date
5ate
=rimary key
)ages 5ate
EmpNo
.nteger
!
Not n$ll
Employee No
No=iece
.nteger
!
N$ll
No#o#=ieces
Rate
.nteger
!
Not n$ll
Rate
Amo$nt
'$rrency
Not n$ll
Amo$nt
/;
;. SYSTEM TESTING < IMPLEMENTATION ;.1. SYSTEM TESTING Testing is a process o e0ec$ting a program with the intent o inding the error# Testing pro&ides the last option rom which 3$ality can (e assessed and more pragmatically, errors can (e $nco&ered# Testing is an indi&id$alistic process, and the n$m(er o dierent types o tests &aries as m$ch as the dierent de&elopment approaches# System testing is act$ally a series o dierent tests whose primary p$rpose is to $lly e0ersice the comp$ter-(ased system# Altho$gh each test has a dierent p$rpose, all work to &eriy that all system elements ha&e (een properly integrated and perorm allocated $nction# There are dierent types o system testing that are worthwhile or the sotware (ased system# •
Reco&ery and Sec$rity Testing
•
Stress Testing
•
=erormance Testing
/
;.2. IMPLEMENTATION .mplementation is the stage, which is cr$cial in the lie cycle o the new system designed# The main stages in the implementation are •
=lanning
•
Training
•
System Testing
.mplementation means con&erting a new or re&ised system into an operational one# 'on&ersion is the main aspect o implementation# .t is the process o designing rom old one to the new one# POST IMPLEMENTATION REVIEW
The post implementation re&iew is sometimes called system a$dit# The re&iew is intended to accomplish two goals# •
E&al$ate the operational inormation system that $sers de&elop#
•
E&al$ate the system de&elopment proced$res to determine how the proje ct co$ld ha&e impro&ed#
Maintenance
is one important phase in implementation# Maintenance
descri(es o$r acti&ities that are $ndertaken ater a program is released or $se# The irst maintenance acti&ity occ$rs (eca$se it is $nreasona(le to ass$me sotware will $nco&er all latent errors in a large sotware system# The process that incl$des the diagnosis and con&ersion is called correcti&e maintenance# Adapti&e maintenance is an acti&ity that modiies sotware to properly interace with the changing en&ironment is (oth necessary and common# The third acti&ity is perecti&e maintenance, this acti&ity is or the majority o all eorts e0pend on sotware maintenance# The o$rth maintenance acti&ity occ$rs when sotware is changed to impro&e $t$re maintaina(ility or relia(ility# /B
. CONCLUSION Th$s the comp$teri*ed =rocess red$ces pro(lems that occ$r and it red$ces time# The &ery ast and any transaction can (e &iewed or retaken in any le&el# Error messages are gi&en at each le&el o inp$t, so that the $ser need not want to go in wrong way#
.n this sotware, the reports are a&aila(le at any time whene&er they are to (e reerred# The $ser can easily $nderstand the details a&aila(le rom the report#
The sotware is men$ dri&en# Simplicity and $ser-riendliness are the hallmark o this project#
!"
. BIBLIOGRAPHY
4is$al 8asic 9#" Gro$nd 6p
Eric )inemiller, Kasont, Ro, 8ill Heyman and Ryan Groom
4is$al 8asic 9#"
Ste&e 8rown
6sing 4is$al 8asic 9#"
Siler I Spotts
!/
=. APPENDIX
DATA FLOW DIAGRAM
'$tting I Stitching =rod$ct
G*'0,+ M*#*&0, S5+,&0
S$pplier
Employee
Reports
)ages
=$rchase +rder?5eli&ery
!!
SOURCE CODE MAIN FORM
=ri&ate S$( mn$'$ttL'lick12 rm'$tting#Show End S$( =ri&ate S$( mn$5eliL'lick12 Repoorder#Show End S$( =ri&ate S$( mn$EmpL'lick12 :rmEmp#Show End S$( =ri&ate S$( mn$E0itL'lick12 End End S$( =ri&ate S$( mn$+rderL'lick12 rm+rder#Show End S$( =ri&ate S$( mn$=rod$ctL'lick12 rm=rod#Show End S$( =ri&ate S$( mn$=$rL'lick12 rm=$rchase#Show End S$( =ri&ate S$( mn$RepoEmpL'lick12 RepoEM=#Show End S$( =ri&ate S$( mn$Repo=rodL'lick12 Repo=rod#Show End S$( =ri&ate S$( mn$RepoS$ppL'lick12 Repos$p#Show !C
End S$( =ri&ate S$( mn$StichL'lick12 rmStich#Show End S$( =ri&ate S$( mn$S$pL'lick12 S$p:rm#Show End S$( =ri&ate S$( mn$)ageL'lick12 rm)ages#Show End S$(
!F
CUTTING FORM
5im my58 5im rsEmp 5im rs'$t 5im E0port
As 5A+#5ata(ase As 5A+#Recordset As 5A+#Recordset
=ri&ate S$( c(oE.5L'lick12 rsEmp#Re3$ery rsEmp#:ind:irst EmpNoOP I 4al1c(oE.5#Te0t2 . Not rsEmp#NoMatch Then t0tEmpName#Te0t P rsEmp1EmpName2 End . End S$( =ri&ate S$( :ormL7oad12 Set my58 P +pen5ata(ase1App#=ath I QGarments#md(2 Set rs'$t P my58#+penRecordset1'$tting, d(+pen5ynaset2 rs'$t#Re3$ery Set rsEmp P my58#+penRecordset1Employee, d(+pen5ynaset2 rsEmp#Re3$ery . Not rsEmp#E+: Then rsEmp#Mo&e:irst 5o )hile Not rsEmp#E+: c(oE.5#Add.tem rsEmp1EmpNo2 rsEmp#Mo&eNe0t 7oop E0port P Array1Apran, 8ed 'o&er, '$sain 'o&er, Glo$se,
c(oType#Add.tem Shirt-:$ll-F" c(oType#Add.tem Shirt-:$ll-F! c(oType#Add.tem Shirt-:$ll-FF c(oType#Add.tem Shirt-Hal-F" c(oType#Add.tem Shirt-Hal-F! c(oType#Add.tem Shirt-Hal-FF c(oType#Add.tem Short Shirt c(oType#Add.tem Night =ant-F" c(oType#Add.tem Night =ant-F! c(oType#Add.tem Night =ant-FF c(oType#Add.tem Towel c(oType#Add.tem +thers End . End S$( =ri&ate S$( cmd5eleteL'lick12 . rs'$t#E+: And rs'$t#8+: Then Msg8o0 Nil Record 'lear Else res P Msg8o01Are yo$ s$re to delete the Record, &(%esNo &(.normation2 . res P &(%es Then . Not rs'$t#E+: And Not rs'$t#8+: Then rs'$t#5elete rs'$t#Re3$ery 'lear Msg8o0 '$tting Entry 5eleted, &(+<+nly &(.normation, 5elete . Not rs'$t#E+: And Not rs'$t#8+: Then rs'$t#Mo&e7ast 5.S=7A%L5ATA Else Msg8o0 7ast Record End . End . End . End . End S$( =ri&ate S$( cmdeditL'lick12 rs'$t#Edit t0t.5#Set:oc$s !9
End S$( =ri&ate S$( cmdE0itL'lick12 6nload Me End S$( =ri&ate S$( cmd:indL'lick12 5im .5 .5 P 4al1.np$t8o01Enter the '$tting .522 rs'$t#Re3$ery rs'$t#:ind:irst .5OP I 4al1.52 . Not rs'$t#NoMatch Then 5.S=7A%L5ATA Else Msg8o0 No '$tting entry o$nd in this N$m(er, &(.normation &(+<+nly End . End S$( =ri&ate S$( cmdNewL'lick12 rs'$t#AddNew 'lear End S$( =ri&ate S$( cmdSa&eL'lick12 +n Error GoTo ShowError rs'$t1id2 P t0t.5#Te0t rs'$t1'5ate2 P 5T='5ate#4al$e rs'$t1EmpNo2 P c(oE.5#Te0t . +ptType1"2#4al$e P Tr$e Then rs'$t1>$ality2 P E0port Else. +ptType1/2#4al$e P Tr$e Then rs'$t1>$ality2 P 7ocal End . rs'$t1Type2 P c(oType#Te0t rs'$t1No=iece2 P 4al1t0t>ty#Te0t2 rs'$t1Rate2 P 4al1t0tRate#Te0t2 rs'$t#6pdate Msg8o0 Record 6pdated, &(+<+nly &(.normation, Sa&e 'lear !;
E0it S$( ShowError@ Msg8o0 Err#N$m(er I - I Err#5escription End S$( =ri&ate S$( cmd:irstL'lick12 . Not rs'$t#8+: Then rs'$t#Mo&e:irst 5.S=7A%L5ATA End . End S$( =ri&ate S$( cmd7astL'lick12 . Not rs'$t#8+: And Not rs'$t#E+: Then rs'$t#Mo&e7ast 5.S=7A%L5ATA End . End S$( =ri&ate S$( cmdNe0tL'lick12 . Not rs'$t#8+: And Not rs'$t#E+: Then rs'$t#Mo&eNe0t . rs'$t#E+: Then Msg8o0 7AST RE'+R5 rs'$t#Mo&e7ast End . 5.S=7A%L5ATA End . End S$( =ri&ate S$( 'M5=R.4.+6SL'lick12 . Not rs'$t#8+: And Not rs'$t#E+: Then rs'$t#Mo&e=re&io$s . rs'$t#8+: Then Msg8o0 :.RST RE'+R5 rs'$t#Mo&e:irst End . 5.S=7A%L5ATA End . End S$( !
=ri&ate S$( 'lear12 t0t.5#Te0t P t0tEmpName#Te0t P t0t>ty#Te0t P t0tRate#Te0t P End S$( =$(lic S$( 5.S=7A%L5ATA12 . Not rs'$t#8+: And Not rs'$t#E+: Then t0t.5#Te0t P rs'$t1id2 5T='5ate#4al$e P rs'$t1'5ate2 c(oE.5#Te0t P rs'$t1EmpNo2 . rs'$t1>$ality2 P E0port Then +ptType1"2#4al$e P Tr$e Else. rs'$t1>$ality2 P 7ocal Then +ptType1/2#4al$e P Tr$e End . c(oType#Te0t P rs'$t1Type2 t0t>ty#Te0t P rs'$t1No=iece2 t0tRate#Te0t P rs'$t1Rate2 End . End S$(
SCREEN LAYOUTS
!B
C"
C/
C!
CC
CF
C
C9
C;
REPORTS
C
CB
F"