22537462 courier service a project report

8/17/2019 22537462 Courier Service a Project Report

http://slidepdf.com/reader/full/22537462-courier-service-a-project-report 1/79

APROJECT REPORT

ON

COURIER SERVICES

SUBMITTED IN THE PARTIAL FULFILLMENT OF THEREQUIREMENT FOR THE AWARD OF THE DEGREE

OFBACHELOR OF COMPUTER APPLICATION

(2003-2006)

SUBMITTED TO: SUBMITTED BY:

MISS TARU VARSHNEY DHANANJAI SINGH

PROJECT GUIDE R.NO.: 3!"02# BCA-VI SEM.

INSTITUTE OF MANAGEMENTSTUDIES



C-238, BULANDSHAHAR G.T. ROAD, LAL QUAN, P.B.NO. 57,

GHAZIABAD-2!"



ACKNOWLEDGMENT

A project always is a result of collaborative efforts. This one has been

especially so. I am indebted to many people who have made this

happen. It is the right time to speak out the word of thanks for them. I

sincerely admit that without their efforts & blessings, this project

would not have taken its presence.

I am also thank to Miss Taru Varshney ( Project Guide BCA) for her guided

us in this project idea.

I would like to express my simple words of respect & gratitude

imprinted deep in my heart to the in-charge, computer center, for

providing me the guidance & never ending support.

DHANANJAI SINGH

BCA-VI SEM.



INDE#

1. ACKNOW!"G!M!NT

#. C!$T%&%CAT! O& O$%G%NA%T'

. %NT$O"CT%ON

*. +A$"WA$! $!,%$!M!NT

-. O&WA$! $!,%$!M!NT

/. %NV!T%GAT%ON %N&O$MAT%ON $!,%$!"

0. O&TWA$! "!V!OPM!NT %&! C'C!

. &O$M 2 CO"%NG

3. B%B%OG$AP+'



Introduction



INTRODUCTIONINTRODUCTION

P$PO! 4

The project on Intranet Module shall be a useful product for managing the courier

services within a organization. It facilitates the users to send the couriers to other person

and to receive from others.

COP!4

This project provides the facility to all users to send and receive the courier. They can also

update and delete the courier, and also get the information of the status of the courier.

"OCM!NT CONV!NT%ON4

The conventions shall be used to design the system are given below in the

following table so that the user can easily understand the system -

A$$%&'()*(+ M&)(

D.I.M. Development ofthe Int!netMo"#le

S$W Soft%!eH$W H!"%!e

%NT!N"!" A"%!NC! AN" $!A"%NG GG!T%ON 45

The document is mainly meant for the following people which shall

involve to design this system and to make the system more

interactive &

!" #rof. $.%. &havan '(.).&."

*" #rof. +unil #andey ' hairperson"

" #rof. ishit /oel ' #roject Incharge "



0" #roject Members

The rest of the document have very less number of abbreviation and

easy to understand as it is written in simple 1nglish language. The

document contain mainly description of product ,hardware

re2uirement system re2uirement etc . +34 re2uirement and hardware

re2uirement is mainly meant for Mr. Manish ( a6 %nchar7e ).

&escription of features of system is mainly meant for Pro8. Nishit

Goe9 and our team members.

PROJECT SCOPE :-

The scope of project shall be describe in following points

1) %115IT+ -

The main benefit of this project is that it facilitate user to communicate in a

faster manner in comparison of manual system. Through this system

the current status of the courier can be known easily whereas in

manual system it is a difficult task.

#) )%61TI$1 -

To provide 2uick service without any delay.

7151711+ '&

• Mastering in $%

• )racle &eveloper /uide by Ivan %ayross

• $isual %asic 8 in *! &ays by /reg #erry



System Features



3. ystem !eatures

.1 Ad:inistrator

.# Wor;in7

. "is<atchin7

.* !n=uiry

.1 Ad:inistrator 4 5

This department have all right to provide or restrict to any department or employee to the

functionality of the project.

.1.1 Add !:<9oyee-

)nly the administrator will add the employee information and provide the login id

and password when any new employee will recruite into the enterprise of the courier

services.

.1.# Create a9ias45

The administrator will provide the aliase of password of the employee who want to

go on the leaves. This feature will provide the working by another employee in place of

regular employee without knowing their password.

.1. Attendance heet 45

The presentation or absent of the employee will be handled by the administrator.

9ny employee can not get their pro:y attendance by the change of system date or any

other type.

.1.* Courier in8or:ation45

9dministrator has the right to get any information about the courier at any time

without any permission of regarding department.

.1.- !:<9oyee in8or:ation45



The employee database can be updated by the administrator department and the

administrator can get the any information about the employee working status.

.1./ <date ca9cu9ation ta69e45

)nly the administrator have right to change the alculation table as per the changes

in the transportation cost.

.# Wor;in7 de<art:ent45

.#.1 Ne> courier entry45

)nly the working department will enter the information of the new courier into the

data base.

.#.# <date courier 45

The working department employee can change the information about the courier as

per the re2uest of the user with in the fi: time.

.#. "e9ete Courier 4

The working department employee can cancel the courier as per the re2uest of the

user with in the fi: time.

. "is<atchin7 de<art:ent 45

..1 <date courier45

It updates the status of the courier where the courier is at the current time.

.#.1 Courier in8or:ation 45

The dispatching department employees can get the information of the courier.



.* !n=uiry45

.*.1 !n=uiry o8 Char7es45

This feature will facilitate to make calculation of the amount for sending a courier

on the basis of the destination, weight ; rate3gm.

.*.# A6out !:<9oyee45

Through this feature the employee can retrieve the information about the other

employees.

.*. A6out Courier45

4hen the user is needed the information about the courier then employee can tell the

current status of the courier by this feature.



External

Interface

Requirements



". #$ternal %ser Interfaces

*.1. ser %nter8ace

(ere, our the user interface of the proposed system shall be $% forms

containing Menu bars, %uttons, <eyboard +hortcuts, heck bo:es, =ist bo:es etc.

according to the re2uirement. >ser can use Mouse to click the button or choose

from the menu and <eyboard to enter the data.

*.#. +ard>are %nter8aces

This software product shall be run properly on I%M # or any other # the

minimum hardware re2uirement for this software product shall be 80 M% 79M, !?

/% or more secondary memory, & 7)M for installation of this product. This

software product shall use 4I&)4 @A operating system for establish the

interface between software and hardware. The interfaces provided by the 4indows

)+ are sufficient. )racle and $% also use same interfaces.

*.. o8t>are %nter8aces

4e shall uses the following software to design this product

• Microsoft $I+>9= %9+I version 8.? as programming language and as front

end user interface.

• )79=1 version as a data base.

• 4I&)4 version @B3@A as an operating system.

• M"AC (Microso8t "ata Access Co:<onent) or O"BC (O<en "ata Base

Connecti?ity) to create an inter face between Microsoft $% and product )79=1.



M"AC or O"BC is a +34 that acts as an interface between )racle and $% forms. In

case of Intranet3=9 workstations, where same data is shared among many users,

global data area is used.

*.*. Co::unication %nter8aces

+ince our proposed system shall be net-enabled so, communication interface

is 7e2uired . #roposed system contains four sites working concurrently. In the

proposed system, single database which is common to all four sites will be available

on server and all sites will be attached to server actively. In case of intranetworking,

4indows T protocols are already in use. In case of mailing to developers for

further 2uery, Microsoft )utlook 1:press is by default used by the 4indows )+.



Other

onfunctional

Requirements



B. )ther onfunctional 7e2uirements

-.1. Per8or:ance $e=uire:ents

The performance re2uirements of this product shall be not very critical. The system

shall be perform efficiently at 80 M% 79M. The product could run also at * M%

79M but to perform well it is necessary to re2uire the above specified 2uantity of

79M.

-.#. a8ety $e=uire:ents

)ur product is absolutely safe to use. Its usage wonCt provide any damage or any

type of loss to the systems already in use. 9lso the security model is prepared

regarding the safety of &atabase so that data is not lost in case of any damage to

the system.

-..ecurity $e=uire:ents

+ecurity of the system shall definitely be maintained through the password system.

The system is devided in the four security module concern. These are administrator,

en2uiry department, working department, dispatching department. 1ach and every

employee of every department will be authenticated with a login id and password.

9ny employee can not change the system date to make pro:y presentation of

yourself.

-.*.o8t>are ,ua9ity Attri6utes

)ur proposed system shall provide a automate softwere product for the different department of the courier company. The

system will be highly 9daptabile, 9vailable, #ortable.



The so8t>are <roduct sha99 ha?e the 8o99o>in7 so8t>are =ua9ity

attri6utes4

Ada<ta6i9ity455since it shall be simple to use for any non computer backgrounduser. This software product shall not re2uired the acute knowledge of computers.

A?ai9a6i9ity4 55 since this product shall use the +34 which are easily available and

runs under very nominal conditions.

Porta6i9ity4 55 this product shall perfectly portable since it shall easy to install this

product normally on any systems with minimum hardware and software

re2uirements.

$eusa6i9ity -- this product shall not for just single time useable. >ser shall reuse

this product many time as he or she wants.

$o6ustness -- this product shall have less robustness .

$e9ia6i9ity -- the reliability of this product shall be dependent upon maintenance of

the database.



Other

Requirements



. 'ther (e)uirements

Till this time, any further re2uirement is not visible. If in case, the need arises, thatCll

be specified afterwards.

Appendi$ A* +lossary

9s this is just a single project and the terms and language used in this project are

easy to interpret, and the abbreviations have already been described . The need

of building a separate /lossary is not viewed.

Appendi$ * Issue -ist

The pending decision is about >ser &ocumentation that in what form the help shall

be provided with the proposed system. It may re2uire use of (TM= pages if on-line

help is to be provided and thisCll not take any special re2uirements hence, could be

easily implemented if decided to do so.



!esi"n



!ata#ase !esi"n

Ta69e Na:e4 c @ em$

&ie9d Na:e Constraint "ata Ty<e

1mpDid #rimary key umber'"empDname $archar'!B"

empDaddress $archar'*?"

1mpDphone umber'!!"

Ta69e Na:e4 em$%lo"in


loginDname #rimary <ey $archar'A"

loginDpassword $archar'!?"

designation heck $archar'!"standbyDpassword $archar'!?"

empDid 5oreign <ey umber'"

aliasDname $archar'A"

aliasDpassword $archar'!?"

Ta69e Na:e4 attendece


loginDname 5oreign key $archar'A"#resent heck $archar'"

aDdate heck &ate



Ta69e Na:e4 $erformance


loginDname 5oreign <ey $archar'A"

pDdate &ate

standbyDstatus heck $archar'"standbyDtime &ate

standbyDresume &ate

aliasDname $archar'A"

aliasDpassword $archar'!?"

Ta69e Na:e4 courier%details

&ie9d Na:e Constraint "ata Ty<ecourierDid #rimary <ey umber'0"

sDname $archar'!B"

sDaddress $archar'*?"

sDphone umber'!!"

rDname $archar'!B"

rDaddress $archar'*?"

rDphone umber'!!"

>pdatable heck $archar'"

+tatus $archar'!?"

amount umber'"

empDid 5oreign key umber'"

Ta69e Na:e4 calculation


destination #rimary <ey $archar'!B"

chargeDperDgram umber'*"

Ta69e Na:e: u$date%date


loginDname $archar'A"

updatedDdate date



!F!S

9dministrator

$alidate forlogin ;

password

1nter=ogin

9nd#assword

empDlogin



9dministrator

9ttendencesheet

reate aliase

add 1mployee

>pdate

calculation table

Demp

attendence

performance

calculation



$alidate login ;

#assword empDlogin

ew ourier

1ntry >pdate ourier

&eleteourier

4orking&epartment

courierDdetails courierDdetails

courierDdetails

ourierInformation

ourierDdetails



$alidate login; #assword

>pdateourier

ourier Information

ourierDdetailsourierDdetails

empDlogin&ispatching&epartment



$alidate =ogin ;

#assword

1n2uiry&epartment empDlogin

9bout harges9bout1mployee

9boutourier

calculation cDemp courierDdetails

1nter =ogin

; #assword



System &nalysis

and !esi"n



'T!M "!V!OPM!NT %&! C'C!

The yste: "e?e9o<:ent i8e Cyc9e ("C) was developed because, historically,

many computer system were being delivered which did not satisfy user re2uirements, and because those few projects that did satisfy user re2uirement were being developed over E

budget or over time. The "C is a methodology that has been constructed to ensure that

systems are designed and implemented in a methodical, logical and step-by-step

approach. there are seven steps, known as phases, in the +&=

• The #reliminary Investigation #hase

• The 9nalysis #hase

• The &esign #hase

• The &evelopment #hase

• The Implementation phase

• The Maintenance #hase

• #ost Implementation 1valuation and Maintenance

1ach phase of the +&= creates a tangible product or deliverable. an important

components of the +&= is that at each phase, a conscious decision is made to continue

development of the project, or to drop it. in the past, projects developed without the

guidance of the +&= were continued well after Fcommon senseC dictated that it made no

sense to proceed further. the deliverables act as milestones against which we can judge

the progress and continuing viability of the project.

The waterfall model represents the first significant attempts at formalizing the software

development process and as such is probably the most widely known of the life-cycle

models. This model is linear and original, and makes the 2uestionable assumption that

each development phase can be completed largely in isolation. This has been recognized

to a certain e:tent in later variant of the waterfall model that shows a limited form of

iteration between stages, but essentially retains their strict chronology. %ecause of itCs

heavy reliance on elaborate documentation as completion criteria, the waterfall model is



suitable for tightly specified systems such as compilers or operating system but breaks

down when applied to highly interactive projects such as graphical end user applications.

The s<ira9 :ode9 represents a considerable evolution of the waterfall model by offering

a risk driven approach that emphasizes the activities of prototyping and the evaluation of

alternatives against initial hypotheses. This model also recognizes the applicability of

e:isting development model to particular tasks and as such can accommodate them as

special cases of the spiral model. the spiral model considers the development process as a

number of successive progressions through each of the modelCs stages, each time at a

greater level of elaboration, thus providing an incremental approach to both software

development and maintenance. This approach is graphically represented as a continuous

spiral traversal through each of the modelCs stages. 9nother advantages over the waterfall

model is that depending on specific project objectives and constraints, and the outcome of

the risk analysis phase, different development approaches or particular combinations will

prove to be more suitable than others. Thus for any given application, not all of the

modelCs stages will be e2ually important, followed in the same se2uence, or iterated

through the same number of times. (owever, despite the fact that it represents a

significant improvement over the waterfall model, the spiral model does not ade2uately

address the sufficient emphasis on the problem domain or the behavioral aspects of

system development.

To understand the structure and working of the +&=, weCll e:amine each phase in turn.

The Pre9i:inary %n?esti7ation

The preliminary Investigation #hase may begin with a phone call from a customer, a

memorandum from a vice president to the &irector of the system development, a letter

from a customer to discuss a perceived problem or deficiency, or a re2uest for something

new in an e:isting system. The purpose of the preliminary Investigation is not to develop

a system, but to verify that a problem or deficiency really e:ist, or to pass judgment on

the new re2uirement. This phase is typically very short, usually not more then a day or

two for a big project, and in some instances it can be as little as two hours. The end result,



or deliverable, from the #reliminary investigation phase is either a willingness to proceed

further, or the decision to Fcall it 2uitsC.

"esi7n

The e:ceptional 'or foolish" programmer might begin coding without a good design.

#rogrammers who do so may find themselves going back to modify piece of code theyCve

already written as they move through the project with a good design, the likelihood of

this happening will be reduced dramatically. The end result is a program that will have in

the way it was intended, and will generally have with the shorter overall program

development time. &esign in the +&= encompasses many different elements. (ere is a

list of the different components that are FdesignedC in the phase / input / output /

#rocessing ( 5iles by the end of the design phase, we would hope to hope to have a

format re2uirements statement for the program, and a rough sketch of what the user

interface will look like.

Most programs are designed by the output of the program. The reasoning here is that if

you know what the output of the program should be, you can determine the input needed

to produce that output more easily. )nce you know both the output from, and the input to

the program, you can then determine what processing needs to be performed to convert

the input to output. Gou will also be in a position to consider what information needs to

be saved, and in what sort of file. 4hile doing the output and input design, more

information will be available to add to the re2uirement statement. It also possible that a

first screen design will take shape and at the end of these designs, and a sketch will be

made of what the screen will like. 9t this stage of the +&= it isnCt necessary to discuss

the FhowC of what the program will do, just to get the re2uirement down on paper.

"e?e9o<:ent

The &evelopment #hase is in many ways the most e:citing time of the +&=. &uring

this phase, computer hardware is purchased and the software is developed. That means

that we actually start coding the program. In the development phase, e:amination and

ree:amination of the re2uirement statement is needed to ensure that it is being followed



to the letter. 9ny deviations would usually have to be approved either by the project

leader or by the customer. The development phase can be split into two sections, that of

#rototyping and #roduction ready 9pplication reation. #rotyping is the stage of the

development phase that produces a pseudo-complete application, which for all intents and

purpose appears to be a fully functional. &evelopers use this stage to demo the

application to the customer as another check that the final software solution answers the

problem posed. 4hen they are given the )< from the customer, the final version code is

written into this shell to complete this phase.

%:<9e:entation

In the implementation phase, the project reaches fruition. 9fter the development phase of

the +&= is complete, the system is implemented. 9ny hardware that has been purchased

will be delivered and installed. +oftware, which was designed in phase , and

programmed in phase 0 of the +&=, will be installed on any #s that re2uire it. 9ny

persons that will be using the program will also be trained during this phase of the +&=.

The system development life cycle during the implementation phase, both the hardware

and the software is tested. 9lthough the programmer will find fi: many problems, almost

invariably, the user will uncover problems that the developer ha been unable to simulate.

This leads on the si:th and final stage.

Audit and Maintenance

#hase 8 of the +&= is the 9udit and Maintenance #hase. In this phase someone 'usually

the client, but sometimes a third party such as an auditor" studies the implemented system

to ensure that it actually fulfills the re2uirement statement. Most important, the system

should have solved the problems or deficiency, or satisfied the desire that was identified

in phase ! of the +&= E the preliminary investigation. More than a few programs and

systems have been fully developed that, for one reason or another, simply never met the

original re2uirements. The maintenance portion of this phase deals with any changes that

need to be made to the system. hanges are sometime the result of the system not

completely fulfilling its original re2uirements, but they could also be the result of

customer satisfaction. +ometimes the customer is so happy with what they have got that

they want more. hanges can also be forced upon the system because



Form

and

Codin"



&im objconn 9s 9&)&%.onnection

&im objrs 9s 7ecordset

&im dateDvalue 9s $ariant

#rivate +ub 5ormD=oad'"

+et objconn H ew 9&)&%.onnection

4ith objconn

.#rovider H msdaora

.onnection+tring H user idHscottJpasswordHtiger

.)pen

1nd 4ith

)n 1rror /oTo errorDlable

+et objrs H ew 9&)&%.7ecordset

objrs.)pen select K from attendece, objconn, ad)pen&ynamic,

ad=ock)ptimistic

1:it +ub

errorDlable

Msg%o: ot a correct login name , ?, alert

Labove is database connectivity

1nd +ub

#rivate +ub ommand!Dlick'"

dateDvalue H 5ormat'ow, d - mmm - yy"

L)n 1rror /oTo &elete1rr



commandstring H insert into attendece values ' ; L ;

TDloginDname.Te:t ; L ; , ; LyesL ; , ; L ; dateDvalue ; L ;

"

4ith objconn

.1:ecute 'commandstring"

1nd 4ith

emptyDte:tDfields Lcall to procedure

1:it +ub

L&elete1rr

L Msg%o: 1rr.&escription

1nd +ub

#rivate +ub emptyDte:tDfields'"

TDloginDname.Te:t H

1nd +ub







4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith



objrs.)pen select loginDname,aliasDname,aliasDpassword from empDlogin

; where loginDname H ; L ; TDloginDname.Te:t ; L , objconn,

ad)pen&ynamic, ad=ock)ptimistic

attachDte:tfieldsDtoDtablefields Lcall to procedure

1:it +ub

errorDlable

Msg%o: ot a correct login name , ?, alert


1nd +ub

#rivate +ub attachDte:tfieldsDtoDtablefields'"

TDloginDname.Te:t H objrs'loginDname"



Te:t!.Te:t H objrs'aliasDname"

Te:t*.Te:t H objrs'aliasDpassword"

1nd +ub

#rivate +ub ommand*Dlick'"

)n 1rror /oTo &elete1rr

commandstring H update empDlogin set aliasDname H ; L ;

Te:t!.Te:t ; L ; ,aliasDpassword H ; L ; Te:t*.Te:t ; L ; where

loginDname H ; L ; TDloginDname.Te:t ; L

4ith objconn


1nd 4ith

emptyDte:tDfields Lcall to procedure

1:it +ub

&elete1rr

Msg%o: 1rr.&escription

1nd +ub


TDloginDname.Te:t H

Te:t!.Te:t H

Te:t*.Te:t H

1nd +ub




If )DcourierDinfo H True Then

wDdept!.+how

1nd If

If )D719T1D9=I9+ H True Then

9&GD719T1D9=I9+.+how

1nd If

If )D9TT1&11D+(11T H True Then

9&GD9TT1&11D+(11T.+how

1nd If

If )DempDinfo H True Then

9&GD1M#DI5).+how

1nd If

If )D9&&D1M#=)G11 H True Then

9&GD1M#Dnew.+how

1nd If

If )D>#&9T1DDT9%=1 H True Then

9&GD>#&9T1D9=DT9%=1.+how

1nd If

1nd +ub





&im objrs! 9s 7ecordset

&im objrs* 9s 7ecordset


9&GD#175)7M91D1M#.+how

>nload Me

1nd +ub

#rivate +ub ommandBDlick'"


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith


attachDte:tfieldsDtoDemploginDtablefields Lcall to procedure

attachDte:tfieldsDtoDempdetailsDtablefields

attachDte:tfieldsDtoDempattendenceDtablefields

1:it +ub

errorDlable

Msg%o: ot a correct =)/I 9M1 , ?, alert




1nd +ub


connectivityDforDdate

1nd +ub

#rivate +ub connectivityDforDdate'"


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith

L)n 1rror /oTo errorDlable


objrs.)pen select K from updateDdate, objconn, ad)pen&ynamic,

ad=ock)ptimistic

=D&9T1.aption H 5ormat'objrs'>#&9T1&D&9T1", d - mmm - yy"

1:it +ub

LerrorDlable

L Msg%o: +G+T1M #7)%=1M )T9T 9&MII+T79T)7

; M9<1 &9T1 >#&9T1 , ?, alert




1nd +ub

#rivate +ub attachDte:tfieldsDtoDemploginDtablefields'"


objrs.)pen select K from empDlogin ; where loginDname H ; L ;

TD=)/ID9M1.Te:t ; L , objconn, ad)pen&ynamic,

ad=ock)ptimistic

Te:[email protected]:t H objrs'designation"

Te:tA.Te:t H objrs'loginDpassword"

Te:tB.Te:t H objrs'standbyDpassword"

)n 1rror /oTo errDalias

Te:tN.Te:t H objrs'aliasDname"

Te:t8.Te:t H objrs'aliasDpassword"

1:it +ub

errDalias

Msg%o: 9=I9+ 5)7 >+17 &)1+LT 1OI+T, vb)<)nly

Te:tN.Te:t H

Te:t8.Te:t H

1nd +ub

#rivate +ub attachDte:tfieldsDtoDempdetailsDtablefields'"

+et objrs! H ew 9&)&%.7ecordset

objrs!.)pen select K from cDemp,empDlogin where cDemp.empDid H

empDlogin.empDid and empDlogin.loginDname H ; L ;



TD=)/ID9M1.Te:t ; L , objconn, ad)pen&ynamic,

ad=ock)ptimistic

Te:t0.Te:t H objrs!'empDname"

Te:t!!.Te:t H objrs!'empDaddress"

Te:t!?.Te:t H objrs!'empDphone"

1nd +ub

#rivate +ub attachDte:tfieldsDtoDempattendenceDtablefields'"

+et objrs* H ew 9&)&%.7ecordset

objrs*.)pen select attendece.present from attendece,empDlogin where

attendece.loginDname H empDlogin.empDid and empDlogin.loginDname H

; L ; TD=)/ID9M1.Te:t ; L, objconn, ad)pen&ynamic,

ad=ock)ptimistic

LTe:t*.Te:t H objrs*'"

LTe:t.Te:t H objrs*'"

1nd +ub




=D&9T1.aption H 5ormat'ow, d - mmm - yy"

1nd +ub



&im 4ith1vents ado#rimary7+ 9s 7ecordset

&im mbhanged%yode 9s %oolean

&im mv%ookMark 9s $ariant

&im mb1dit5lag 9s %oolean

&im mb9ddew5lag 9s %oolean

&im mb&atahanged 9s %oolean


&im db 9s onnection

+et db H ew onnection

db.ursor=ocation H ad>selient

db.)pen

#7)$I&17HM+&9+P=JdsnHcourierJuidH+)TTJpwdHTI/17J

+et ado#rimary7+ H ew 7ecordset

ado#rimary7+.)pen select

=)/ID9M1,#D&9T1,+T9&%GDTIM1,+T9&%GD71+>M1 from

#175)7M91, db, ad)pen+tatic, ad=ock)ptimistic

+et grd&ata/rid.&ata+ource H ado#rimary7+

mb&atahanged H 5alse

1nd +ub



#rivate +ub 5ormD7esize'"

)n 1rror 7esume e:t

LThis will resize the grid when the form is resized

grd&ata/rid.(eight H Me.+cale(eight - ? - pic%uttons.(eight -

pic+tat%o:.(eight

lbl+tatus.4idth H Me.4idth - !B??

cmde:t.=eft H lbl+tatus.4idth Q N??

cmd=ast.=eft H cmde:t.=eft Q 0?

1nd +ub

#rivate +ub 5ormD<ey&own'<eyode 9s Integer, +hift 9s Integer"

If mb1dit5lag )r mb9ddew5lag Then 1:it +ub

+elect ase <eyode

ase vb<ey1scape

cmdloseDlick

ase vb<ey1nd

cmd=astDlick

ase vb<ey(ome

cmd5irstDlick

ase vb<ey>p, vb<ey#age>p

If +hift H vbtrlMask Then

cmd5irstDlick

1lse

cmd#reviousDlick



1nd If

ase vb<ey&own, vb<ey#age&own

If +hift H vbtrlMask Then

cmd=astDlick

1lse

cmde:tDlick

1nd If

1nd +elect

1nd +ub

#rivate +ub 5ormD>nload'ancel 9s Integer"

+creen.Mouse#ointer H vb&efault

1nd +ub

#rivate +ub ado#rimary7+DMoveomplete'%y$al ad7eason 9s

9&)&%.1vent7eason1num, %y$al p1rror 9s 9&)&%.1rror, ad+tatus 9s

9&)&%.1vent+tatus1num, %y$al p7ecordset 9s 9&)&%.7ecordset"

LThis will display the current record position for this recordset

lbl+tatus.aption H 7ecord ; +tr'ado#rimary7+.9bsolute#osition"

1nd +ub

#rivate +ub ado#rimary7+D4illhange7ecord'%y$al ad7eason 9s

9&)&%.1vent7eason1num, %y$al c7ecords 9s =ong, ad+tatus 9s

9&)&%.1vent+tatus1num, %y$al p7ecordset 9s 9&)&%.7ecordset"

LThis is where you put validation code



1:it +ub

/o#rev1rror


1nd +ub

#rivate +ub +et%uttons'b$al 9s %oolean"

cmd&elete.$isible H b$al

cmdlose.$isible H b$al

cmd7efresh.$isible H b$al

cmde:t.1nabled H b$al

cmd5irst.1nabled H b$al

cmd=ast.1nabled H b$al

cmd#revious.1nabled H b$al

1nd +ub



&im 4ith1vents ado#rimary7+ 9s 7ecordset

&im mbhanged%yode 9s %oolean

&im mv%ookMark 9s $ariant

&im mb1dit5lag 9s %oolean

&im mb9ddew5lag 9s %oolean

&im mb&atahanged 9s %oolean


&im db 9s onnection

+et db H ew onnection

db.ursor=ocation H ad>selient

db.)pen #7)$I&17HM+&9+P=JdsnHcourierJuidHscottJpwdHTI/17J

+et ado#rimary7+ H ew 7ecordset

ado#rimary7+.)pen select &1+TI9TI),(97/1D#17D/79M

from 9=>=9TI), db, ad)pen+tatic, ad=ock)ptimistic

&im oTe:t 9s Te:t%o:

L%ind the te:t bo:es to the data provider

5or 1ach oTe:t In Me.t:t5ields

+et oTe:t.&ata+ource H ado#rimary7+

e:t


1nd +ub



ado#rimary7+.Move5irst


1:it +ub

/o5irst1rror


1nd +ub

#rivate +ub cmd=astDlick'"

)n 1rror /oTo /o=ast1rror

ado#rimary7+.Move=ast


1:it +ub

/o=ast1rror


1nd +ub

#rivate +ub cmde:tDlick'"

)n 1rror /oTo /oe:t1rror

If ot ado#rimary7+.1)5 Then ado#rimary7+.Movee:t



1:it +ub

/o#rev1rror


1nd +ub

#rivate +ub +et%uttons'b$al 9s %oolean"

cmd9dd.$isible H b$al

cmd1dit.$isible H b$al

cmd>pdate.$isible H ot b$al

cmdancel.$isible H ot b$al

cmd&elete.$isible H b$al

cmdlose.$isible H b$al

cmde:t.1nabled H b$al

cmd5irst.1nabled H b$al

cmd=ast.1nabled H b$al

cmd#revious.1nabled H b$al

1nd +ub






#rogress%ar!.$alue H ?

Timer!.1nabled H True

1nd +ub


Timer!.1nabled H 5alse

#rogress%ar!.$alue H ?

1nd +ub

#rivate +ub Timer!DTimer'"

#rogress%ar!.$alue H #rogress%ar!.$alue Q !?

If #rogress%ar!.$alue RH !?? Then

Timer!.1nabled H 5alse

If login.oDadyDemp.$alue H True Then

updatingDdateDinDdatabase L this is done only when ady login

adyDdept!.+how

>nload login

>nload Me

1nd If

If login.oDdDemp.$alue H True Then dDdept!.+how

>nload login

>nload Me

1nd If



If login.oDwDemp.$alue H True Then

wDdept!.+how

>nload login

>nload Me

1nd If

If login.oDeDemp.$alue H True Then

eDdept!.+how

>nload login

>nload Me

1nd If

1nd If

1nd +ub

#rivate +ub updatingDdateDinDdatabase'"

loginDvalue H login.TD=)/ID9M1.Te:t

dateDvalue H 5ormat'ow, d - mmm - yy"

L above statement refresh the values like fflush'" in c


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith





objrs.)pen select K from updateDdate, objconn, ad)pen&ynamic,

ad=ock)ptimistic

commandstring H update updateDdate set loginDname H ; L ;

loginDvalue ; L ; ,updatedDdate H ; L ; dateDvalue ; L

objconn.1:ecute 'commandstring"

1:it +ub

LerrorDlable

1nd +ub



&im reply 9s $ariant


&im 4ith1vents objrs 9s 7ecordset

#rivate +ub )=)7D)5DT1OT5I1=&DT)D4(IT1'"

tDcourierDid.%ackolor H ;(A?????!A

Te:t*.%ackolor H ;(A?????!A

Te:t.%ackolor H ;(A?????!A

Te:t0.%ackolor H ;(A?????!A

Te:tB.%ackolor H ;(A?????!A


Te:tN.%ackolor H ;(A?????!A

Te:tA.%ackolor H ;(A?????!A

Te:t@.%ackolor H ;(A?????!A

Te:t!?.%ackolor H ;(A?????!A

1nd +ub

#rivate +ub 19%=1DT(1DT1OT5I1=&'"

tDcourierDid.$isible H True

tDcourierDid.1nabled H True

Te:t*.1nabled H TrueTe:t.1nabled H True

Te:t0.1nabled H True

Te:tB.1nabled H True




1nd +ub


tDcourierDid.Te:t H

Te:t*.Te:t H

Te:t.Te:t H

Te:t0.Te:t H

Te:tB.Te:t H

Te:t8.Te:t H

Te:tN.Te:t H

Te:tA.Te:t H

Te:[email protected]:t H

Te:t!?.Te:t H

1nd +ub

#rivate +ub connectivityDforDinfo'"


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith



objrs.)pen select K from courierDdetails ; where courierDid H ; L ;

tDcourierDid.Te:t ; L , objconn, ad)pen&ynamic, ad=ock)ptimistic

attachDte:tfieldsDtoDtablefields Lcall to procedure



Te:t0.Te:t H objrs'sDphone"

Te:tB.Te:t H objrs'rDname"

Te:t8.Te:t H objrs'rDaddress"

Te:tN.Te:t H objrs'rDphone"

Te:tA.Te:t H objrs'updatable"

Te:[email protected]:t H objrs'status"

Te:t!?.Te:t H objrs'9M)>T"

1nd +ub





&im rate 9s $ariant


emptyDfieldDforDemployee


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith



objrs.)pen select

cDemp.empDid,cDemp.empDname,cDemp.empDaddress,empDlogin.loginDna

me,cDemp.empDphone,attendece.present from cDemp,empDlogin,attendece

where D1M#.1M#DI& H ; L ; TD1M#DI&.Te:t ; L ; and

empDlogin.empDid H cDemp.empDid and empDlogin.loginDname H

attendece.loginDname, objconn, ad)pen&ynamic, ad=ock)ptimistic

attachDte:tfieldsDtoDtablefieldsDemployee Lcall to procedure

1:it +ub

LerrorDlable

L Msg%o: ot a correct 1M#=)G11 I& , ?, alert




1nd +ub


emptyDfieldDforDcalculation

If Te:t0.Te:t H Then

Msg%o: 1T17 T(1 41I/(T 5)7 )>7I17, vb)<)nly

1:it +ub

1nd If


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith



objrs.)pen select K from calculation where destination H ; L ;

Te:t!.Te:t ; L, objconn, ad)pen&ynamic, ad=ock)ptimistic

objrs.Move5irst

Te:t!.Te:t H objrs'destination"

rate H objrs'chargeDperDgram"

Te:t*.Te:t H rate K $al'Te:t0.Te:t"

1:it +ub



)ption 1:plicit


&im objrs 9s 9&)&%.7ecordset

&im objconn! 9s 9&)&%.onnection

&im objrs! 9s 9&)&%.7ecordset

&im dateDvalue 9s $ariant

&im lDname 9s +tring

&im lDpassword 9s +tring

&im lDdes 9s +tring

&im lDname! 9s +tring

&im lDpassword! 9s +tring

&im lDdes! 9s +tring

&im lDattendence 9s +tring Lthis uses seprate connection and recordset

&im oDdesDvalue 9s +tring


dDconnection

dDconnectionDforDattendence

If lDattendence SR yes Then

If oDadyDemp.$alue H 5alse Then

1:it +ub

1nd If 1nd If

dataDvalidation

1nd +ub



1nd 4ith


+et objrs! H ew 9&)&%.7ecordset

If oDadyDemp.$alue H 5alse Then L not going to check attendence for

administrator

objrs!.)pen select K from attendece ; where loginDname H ; L

; TDloginDname.Te:t ; L ; and ; aDdate H ; L ; dateDvalue ;

L, objconn, ad)pen&ynamic, ad=ock)ptimistic

1nd If

lDattendence H objrs!'present"

If oDadyDemp.$alue H True Then

lDattendence H yes L for administrator

1nd If

1:it +ub

errorDlable

If oDadyDemp.$alue H True Then

lDattendence H yes L for administrator

1lse

Msg%o: (1< 4IT( 9&MII+T79T)7 5)7 >7

9TT1&11 )7 >7 +G+T1M &9T1 I+ )T )771T, ?, alert

1nd If

1nd +ub




&im 4ith1vents objrs 9s 7ecordset

#rivate +ub )=)7D)5DT1OT5I1=&DT)D4(IT1'"

tDcourierDid.%ackolor H ;(A?????!A

Te:t*.%ackolor H ;(A?????!A

Te:t.%ackolor H ;(A?????!A


Te:tB.%ackolor H ;(A?????!A


Te:tN.%ackolor H ;(A?????!A

Te:tA.%ackolor H ;(A?????!A

Te:t@.%ackolor H ;(A?????!A

Te:t!?.%ackolor H ;(A?????!A

1nd +ub

#rivate +ub 19%=1DT(1DT1OT5I1=&'"

tDcourierDid.$isible H True

tDcourierDid.1nabled H True

Te:t*.1nabled H True

Te:t.1nabled H TrueTe:t0.1nabled H True

Te:tB.1nabled H True


Te:tN.1nabled H True



9&&D71)7& L procedure call

1nd If

)=)7D)5DT1OT5I1=&DT)D%=9<

&I+9%=1DT(1DT1OT5I1=&

=)<DT(1DT1OT5I1=&

emptyDte:tDfields

D1OT.$isible H 5alse

DI5).$isible H 5alse

D)<.1nabled H True

D&1=1T1.1nabled H 5alse

D+>%MIT.1nabled H 5alse

D%9<.1nabled H 5alse

)D&1=1T1D)>7I17.$isible H True

)D14D)>7I17.$isible H True

)D>#&9T1D)>7I17.$isible H True

)DI5)D)>7I17.$isible H True

1nd If

1nd +ub

#rivate +ub D&1=1T1Dlick'"

If )D&1=1T1D)>7I17.$isible H True Then

reply H Msg%o:'971 G)> +>71 G)> 49T T) &1=1T1, !,

)5I7MI/ G)>7 &1=1T1"

1nd If



Msg%o: 1nter 9mount less than !???, vb)<)nly

1nd If

)n 1rror /oTo 9dd1rr

commandstring H insert into courierDdetails values ' ; L ;

tDcourierDid.Te:t ; L ; , ; L ; Te:t*.Te:t ; L ; , ; L ;

Te:t.Te:t ; L ; , ; L ; Te:t0.Te:t ; L ; , ; L ; Te:tB.Te:t ;

L ; , ; L ; Te:t8.Te:t ; L ; , ; L ; Te:tN.Te:t ; L ; , ; L

; Te:tA.Te:t ; L ; , ; L ; Te:[email protected]:t ; L ; , ; L ;

Te:t!?.Te:t ; L ; , ; L ; ! ; L ; "

4ith objconn


1nd 4ith

1:it +ub

9dd1rr

Msg%o: 1IT(17 not a uni2ue courierDid )7 data is invalid, vb)<)nly

1nd +ub

#rivate +ub )#TI)DIT1MD1OITDlick'"

>nload Me

1nd +ub



&im rate 9s $ariant


emptyDfieldDforDcalculation

If Te:t0.Te:t H Then

Msg%o: 1T17 T(1 41I/(T 5)7 )>7I17, vb)<)nly

1:it +ub

1nd If


4ith objconn

.#rovider H msdaora


.)pen

1nd 4ith



objrs.)pen select K from calculation where destination H ; L ;

Te:t!.Te:t ; L, objconn, ad)pen&ynamic, ad=ock)ptimistic

objrs.Move5irst

Te:t!.Te:t H objrs'destination"

rate H objrs'chargeDperDgram"

Te:t*.Te:t H rate K $al'Te:t0.Te:t"

1:it +ub

errorDlable



Msg%o: o +uch &estination, ?, alert


1nd +ub

#rivate +ub emptyDfieldDforDcalculation'"

Te:t*.Te:t H

1nd +ub



B%B%OG$AP+'

Mastering Visual Basic 6

Author(s) : Evangelos Petroutsos

Publisher : BPB Publications

Software Engineering A Practitioner’s Approach (fifth eition)

Author(s) : !oger S" Press#an

Publisher : $ata Mc%raw&'ill

una#entals f Software Engineering

Author(s) : *arlo %he++i, Mehi -a+a.eri, an /ino Manrioli Publisher : Prentice 'all of 0nia

22537462 courier service a project report

Documents