Acknowledgement
First of all, I
express my gratitude to Mr. M. AnantaRao, Sr. General Manager(IT) GRIDCO,
Bhubaneswar for making arrangement for doing my project work here at GRIDCO,
Bhubaneswar.
I am deeply
indebted to my project guide, B. K.
Sisugoswamy, officer incharge
training who has been great source of inspiration and encouragement
during this project work which made it possible to bring out this project. He
has spared his precious time in timely guidance concerning not only my project
work but also other aspects of computer applications.
Prasanta Kumar Paikaray
M.C.A., 6th Semester
D E
C L A R A I
O N
We, Prasanta Kumar Paikaray & Soumendra Kumar Mohanty,
final year students of MCA, IGNOU, do hereby declare that we have developed a
package “IT Maintenance & Management Information System”, jointly under the
supervision of Sri B.K.Sisugoswamy, A.E,IT Department Gridco, Bhubaneswar.
………………………..
Prasanta Kumar Paikaray
Enrollment No. : MCA 984230862
…………………………
Saumendra Kumar Mohanty
Enrollment No. : MCA 984231223
GRIDCO CORPORATION OF ORISSA LTD.
JANAPATH, BHUBANESWAR.
Certificate
This is to certify that Mr. Prasanta Kumar
Paikaray, a final semester student of Master in Computer
Applications (MCA), of Indira Gandhi National Open University, New Delhi
has successfully completed a project work titled ‘IT Maintenance and Management
Information System' in ORACLE and Visual Basic 6 for Grid
Corporation of Orissa limited for the period of 6 month starting from 1st
July 2000 under my guidance. This report is a testimony of work done by him.
B.K.Sisugoswamy
Assistant
Engineer(IT),
Gridco,Bhubaneswar
GRIDCORPORATION OF ORISSA LTD
JANAPATH, BHUBANESWAR.
Certificate
This is to certify that Mr.
Prasanta Kumar Paikaray, a final semester student of Master In Computer Applications
(MCA) of Indira Gandhi National Open University, New Delhi has successfully
completed a project work titled ‘IT Maintenance and Management Information
System' in ORACLE and Visual Basic 6 for Grid Corporation of
Orissa limited for the period of 6 month starting from July 2000. This report
is a testimony of work done by him.
Mr.
M. Ananta Rao
Sr. General
Manager (IT),
Gridco,
Bhubaneswar.
CONTENTS
1.0
Introduction and Overview
1.1
Introduction
1.2
Objectives
1.3
Project Category
1.4 Organization Overview
2.0
System Analysis and Problem Definition
2.1
Introduction
2.1.1
Existing System Study
2.2
Drawbacks of the Existing System
2.3
Proposed System
2.3.1
Scope of the Proposed System
2.3.2
Limitation of the Proposed System
2.4
Tools / Environment Used
2.5
Feasibility Analysis
2.5.1
Economic Feasibility
2.5.2
Technical Feasibility
2.5.3
Behavioral Feasibility
2.6
Conclusion
3.0
System Design
3.1
Logical Design
3.1.1
Introduction
3.1.2
Data Flow Diagram
3.1.3
Entity-Relationship Diagram
3.2
Physical Design
3.2.1
Input Design
3.2.2
Output Design
3.2.3
Normalization
3.2.4
Database Design (Table Structures)
3.2.5
Security Measures
3.2.6 Validation Checks
4.0
System Development
4.1
Program Structure (HIPO )
4.2
Functional Diagram
4.3
Coding
5.0
System Testing and Implementation
6.0
User Manual
6.1
Documentation
6.2
Data Entry Form
6.3
Report
7.0
Future Application of the project
8.0
References
CHAPTER-1
v
INTRODUCTION
v
OBJECTIVES
v
PROJECT CATEGORY
v
ORGANIZATON
OVERVIEW
¨
COMPUTERISATION IN GRIDCO
¨
NEED FOR COMPUTERISATION
¨
FUTURE PLAN
v INTRODUCTION :
“IT MAINTENANCE AND MANAGEMENT
INFORMATION SYSTEM” is developed for IT department of GRIDCO. This system is
flexible for the users of the organization. The users need not go manually to
generate all Maintenance & MIS reports about purchase allotment,
maintenance of all IT equipment and accessories, which is very difficult to
maintain manually.
v
OBJECTIVES :
The
main objective of this project is to acknowledge the total information about
the different IT related equipments & S/W used in the corporate office and
other branch offices in Grid Corporation of Orissa, Bhubaneswar.
v
PROJECT CATEGORY :
RDBMS (ORACLE 8.0)
v ORGANISATION OVERVIEW
Ø GRIDCO IN
BRIEF
The GRID Corporation of Orissa Ltd. was incorporated under companies Act 1956 on 20.04.1999. Transmission & distribution (T & D) assets of OSEB were transferred to the GRIDCO on 01.04.1996. The GRIDCO is required to take care of bulky procurement of power from different generating stations in the state and to transmit the same to the load Centers. However the GRIDCO has the clear mandate to separate power distribution from transmission activities.
GRID Corporation of Orissa Ltd. is pioneer in the country in the power sector reform process. It has several offices throughout Orissa. Its corporate office is situated at Bhubaneswar.
Functions of GRIDCO:-
· Procurement of power from different generators.
· Transmission of power from the generation stations to the load centers (load despatch).
· Maintenance of GRID.
· Planning and construction of new transmission lines and sub-stations.
In due course, GRIDCO has landed over power distribution function to its four subsidiary companies like CESCO, NESCO, WESCO and SOUTHCO.
Functions of IT Department
In order to reducing the drudgery of work, achieving paperless office and increasing productivity and efficiency in distribution of electricity, computers are used in different branch offices and deportment under GRIDCO. To supervise this h/w components and s/w, department established under GRIDCO known as Information Technology (IT) department.
Its aim is to utilize IT to increase the efficiency of the existing electricity distribution system and provide greater transparency in working system by utilizing different customized software by IT department or by different nominated vendor which is proper suitable to the existing system.
GRIDCO has computerized the following systems in Head Quarter office at Bhubaneswar as well as in different field offices throughout the state.
· Pay bill system.
· Personal information system for all employees and establishment matters.
· Cash management and financial matters.
· Computerization of stores issue and receipt functions.
· Computerization of procurement activities.
· Power purchase and sale activities and billing system.
· Load flow analysis and SCADA system.
· Transmission line and substation design and construction activities using CAD
software.
· All secretarial jobs.
To accomplice above
functions, GRIDCO have installed a number of computers, servers, peripherals
and networking equipment at different places and offices.
IT department of GRIDCO with its head
office at Bhubaneswar is entrusted with all activities pertaining to purchase
allotment, maintenance of all IT equipment and accessories. It generates all MIS reports about purchase,
allocation and maintenance of all IT equipment as and when required.
Some
important MIS reports generated by IT department are:-
Ø
List of users provided with IT equipment.
Ø
Stock report of IT equipment.
Ø
Type, category, make of IT equipment in stock and provided
to users.
Ø
List of requisitions received from users to provide new
equipment.
Ø
List of new equipment purchased with purchase order
details.
Ø
Details of items against purchase orders already received
and under pipe line.
Ø
Maintenance information such as warranty of IT equipment
and AMC etc.
Ø
Validity of AMC period for equipment under existing AMC ,
information relating to equipment to be covered under AMC in near future.
Ø
List of user's request for maintenance of defective
equipment.
Ø
All information pertaining to call given to maintenance
vendors for repair of defective equipment,
machine down time, call closure, spare parts requirement, consumable
requirement etc.
Ø
Maintaining AMC vendors address, telephone nos. etc.
Ø Maintaining list of non repairable, old and obsolete IT equipment and their disposal.
All these
activities were being done manually earlier.
Now after creation of a separate
IT department, GRIDCO is making these activities and generation of MIS reports
computerized. This project work emphasizes the process and method of such
computerization for “Maintenance and Management Information System for IT
equipment used in GRIDCO."
CHAPTER-2
v SYSTEM
ANALYSIS Ø 2.1 Introduction Ø 2.2 Preliminary Investigation Ø
2.3
Requirement Analysis §
2.3.1Tools/Environment
Used
v
2.1 Introduction
System
Analysis is the primary task of system analyst in order to study and analyze the
existing system of the organization. It is the process of gathering and
interpreting the facts, diagnosing the problems and using the information to
recommend improvements to the system
v
2.2 Preliminary Investigation
The purpose of the preliminary investigation is to evaluate
project requests. It involves collection of information that permits the
management to evaluate the merits of the project request and make an informed
judgment about the feasibility of the proposed system. This project has gone through
the following three steps of preliminary investigation.
Ø Request Clarification: -
The GRIDCO management_user group of IT department initiates the project.
Ø Feasibility
Study: -
§ Technical Feasibility: -
Grid Corporation is having a client-server facility
(Sunsolarie). Which is an ideal platform for the system and also having
powerful database Oracle 8.0 and front-end tools like D2K & VB6.0. With the
existing H/W & S/W technology & manpower the project can be easily
handle.
§ Economical Feasibility :-
Since Oracle 8.0 & VB 6.0 is already use at GRIDCO no
costs were to be incurred towards the purchase of S/W. The cost of developing & induction of the system are
quite affordable. The system reduces cost effort and time after it is
developed. Thus the system is found economically feasible.
§ Operational Feasibility :-
The project has got sufficient support from management and user(IT Department ), and the user also involved in the planning of the system. Thus the system is found operational feasible.
§ Request Approval :-
The system was found to be technically, economically &
operationally feasible. Hence the project is approved.
v 2.2
Requirement Analysis
Requirement analysis involves studying the current manual
System to find how it works. The
various methods adopted are Interview of users in IT Department Observation is
made on how the existing system operates. The various methods adopted are
§
Interview of the users in IT Department.
§
Observation of how the existing system operates.
Basing on
the above the following conclusion were made.
Ø
ACTIVITIES
FOLLOWED
· VENDOR INFORMATION (GENERATION)
· ITEM INFORMATION (GENERATION )
· USER INFORMATION ( GENERATION )
· LOCATION INFORMATION ( GENERATION )
· PURCHASED ORDER INFORMATION ( GENERATION )
· VENDORWISE INFORMATION FOR H/W & S/W
· USERWISE INFORMATION ON ITEM
· ITEMS WHICH ARE UNDER WARRANTY
· ITEMS WHICH HAS NO WARRANTY
· ITEMS WHICH ARE UNDER AMC
· ITEMS WHICH HAS NO AMC
· MAINTENANCE MONITORING
Ø Tools/Environment Used
§
Oracle Features
§
Client – Server
Architecture
§
Visual Basic
§
Operating System
§
ORACLE FEATURE
ORACLE is an RDBMS with a client server architecture.
There is a single server to which the clients(tools) are linked. The software
acts as an interface between the server and the clients The clients are linked
to the ORACLE software .In ORACLE the server is called the SQL server The
client can be called a node of the server. Any damage to the server halts the
system & no clients can access the same database.
§
CLIENT SERVER
ARCHITECTURE
Client server architecture has the following qualities
:
·
Improves response time.
·
Reduces network traffic.
·
Improves utilisation of
installed hardware.
·
Eliminates dependence on a
single vendor
·
Enables moving application
from expensive large Mainframes to smaller, less expensive systems.
·
Applications based on Client‑Server
Architecture are easily "Scalable".
·
Key
characteristics of the server
-
Request Queue management
-
Buffer management
-
Execution of the service
-
Results management
-
Notification of service
completion
-
Synchronisation with the
client
·
Key
Characteristics of the client
It is always the client who
-
Initiates communication with
server.
-
Request services
-
Acknowledge service completion
notification
-
Accept Results
v
OVERVIEW OF VISUAL BASIC
Visual Basic is a window based, application development for the creation of client/server software. Visual Basic is considered as a graphical tool used as a front end and has capable of connecting and retrieving data from multiple databases. Visual Basic follows event driven code execution. It provides excellent support for the GUI environment. Visual Basic supports Integrated Development Environment (IDE). IDE is a term commonly used in programming world to describe the interface and environment that we use to create our application. The most interesting and useful feature of Visual Basic is its object repository libraries which permit sharing objects across applications.
§
Command
Button
§
Form
§
Database
§
Chart
Command Button:-
Controls
on a form, such as Command Button and frames, are objects.
Form:-
Each
form in a visual basic project is a separate object
Database:-
Databases
are objects and contain other objects like fields and indexes.
The window objects created in visual basic can be of the following
types :
FORM : Any form in the application ( including MDI
children and MDI form).
CONTROL : Any control in the application.
MDI FORM : The MDI form in the
application(if the application has
one).
FORMS AS OBJECTS :
Forms are
most often used to make up the interface of an application, but they are also
objects that that can be called by other modules in our application. Forms are
closely related to class modules. The major difference between two is that
forms can be visible objects, whereas class modules have no visible interface.
MDI frame and MDI frame with
micro help :
These
have the following characteristics :
·
They are the anchor windows for MDI applications.
·
They must have a menu.
·
They have a title bar.
·
They can be moved, resized, moved, minimized and maximized
§
EVENTS OF VISUAL BASIC:-
Visual Basic
applications are event driven . when a user clicks on a command button, chooses
an item from a menu or events data into
an edit box
§
ODBC:-
Visual
Basic is a tool, which can only be used as front end to application whose data
resides in relational databases. The supported database can be broken down
between ODBC (Open Database Connectivity) data sources and DBMS. ODBC drivers
are software products that form a database-specific link between the
application and the database. They are loaded and controlled by ODBC driver
Manager and, in the case of the 32-bit Oracle driver from Oracle, reside in a
file called SQO32_XX.DLL. ODBC was created to tackle the problem of interfacing
to relational databases, such as SQL server and Oracle, in generic way.
The
functions of the ODBC driver include
·
Establishing the connection
·
Client-cursor management
·
Translation of commands and data formats to suit a
particular database
·
Error-code management
Visual
Basic provides a variety of options to access remote Client\Server database
connects to any backend DBMS, whose database management core obeys open
database connectivity rules are:
·
Data Access Objects (DAO)
·
Data Control
·
Remote Data Objects (RDO)
·
Active Data Objects (ADO)
§
ENCAPSULATION:-
Encapsulation
refers to the incorporation of attribute and methods within a class definition.
An encapsulated class hides its definition and processing details within
itself.
ENCAPSULATION IN VISUAL BASIC:-
Well-defined
windows, menus and user objects represent encapsulated object. Each object can
have a certain no of publicly accessible variables, functions and structures
while others are defined as private or protected information. To communicate
with an object, the publicly accessible variables, functions structure must be
preceded by the object’s name. Events associated with an object or events
associated with components within an object can always be triggered from other
objects.
§
POLYMORPHISM :-
With
Polymorphism, different object respond differently to the same message.
Polymorphism occurs when a particular function or event script is defined for
many objects, but the processing performed is appropriate for each object.
POLYMORPHISM IN VISUAL BASIC:-
Polymorphism
is helpful when creating new object s from old ones because it makes a
programmer’s job simpler. When a new object is defined that is related to an
existing object, it is not necessary to rebuild any of the already existing
code in order to take into account that a new object exists. Polymorphism make
objects more independent and allows new object to be added with little or no
effect on existing objects. The applications developed are more flexible and
more capable of evolving overtime to meet further needs.
§
OBJECTS:-
Objects
are the basic run time entitles in an object-oriented system. Each object
contains data and code to manipulate the data. Objects can interact without
having to know details of each other’s data and code. An object is an instance
of particular class, the objects methods are defined in the class and its
attribute values are defined in the instance.
§
CLASS:-
A group
of objects that shares common properties and relationships. This is the basic
components of object orientations. A class is a unit, consisting of related
attributes and methods.
§
INSTANCE:-
An
instance is a single representation of a particular class.
CHAPTER-3
Ø 3.1
LOGICAL DESIGN
The logical
design of the information system address the details that state how a system
will meet the requirements identified during system analysis. The issues
focused are:
§
3.1.1 Data Flow Diagram (DFD):- The
logical system model is termed as Data Flow Diagram (DFD) that address ‘What
occurs in the System’. It shows the
flow of data into the system, between process and data stores.
§
3.1.2 Entity Relationship Diagram (ERD)
Entity: -
An Entity is any person, place,
thing or event of interest to the organization and about which data are
captured, stored or process.
Entity Relationship: -
This defines the dependencies
& extent to which entities are related.
Entity Relationship Diagram: -
These are design tools that
accomplish the developing methods for data storage and retrieval.
·
Entity
set:
{Vendor, Item, User, Location, Purchase
Order}
¨ Relationship set:
Ø Supply
(Vendor, Item)
Ø Has
(Item, Purchase Order)
Ø Used By (Item,
User, Location)
¨ Symbols Used:
Entity
Relationship
One to One
One to Many
§
ENTITY
RELATIONSHIP DIAGRAM
1 M
M
1
1 1
1
Ø 3.2
PHYSICAL DESIGN
The process of designing the software is called physical design. The issues discussed here are:
§
Input
Design-Output Design
§
Normalization
§
Database Design
§ Security Measures Design
§
3.2.1
INPUT-OUTPUT DESIGN:
While designing the system proper care has been taken for all output requirements of the system as per the user requirements. After conducting a detailed system study on site and by studying the input and output requirements of the system, the final design of the system was done.
·
Input Design:
Considering the output requirements, procedure to
capture the necessary input data in most efficient way was designed. The input design has been done keeping in
view that, the interaction of the user with the system is simply yet
effective. The following points were
considered during input design.
o
Controlling amount of input
o
Avoiding delay
o
Avoiding errors in data
o
Eliminating extra steps
o Keeping the process simple
·
Screen Design:
All the screens of the system are designed with view
to provide the user with easy operation in a simple and efficient way with
minimum possible keystrokes. Instructions
and important messages are flashed on the screen. Almost every screen is provided with help message and option
selection facilities.
Much emphasis is given for speedy processing and
speedy transaction between the screens.
Each screen is designed to make it as much user friendly as possible by
using involving appropriate procedures and triggers as and when required. So to say the user can operate the system
without going through ‘operating manual’ or ‘user manual’. (A detailed screen description and operating procedures are
discussed in user manual)
·
Output Design:
Computer output is the most important and direct
source of information to the user.
While preparing the output reports, the users’ consent is given
priority. (Sample copies of the
reports prepared by this system are attached in user manual)
§
3.2.2 NORMALIZATION:
Once a
record layout is defined, it can use the technique of normalization. This is
the process of breaking down a complex design into a group of simple relationships.
Normalization is the outcome of the work originally done by E. F. Codd. He proposed three normal
forms that defined characteristics of good relational design; these are the First, Second, and Third normal forms. Codd later
coproduced the Boyce-Codd form, which is an enhanced of Third normal Form.
Subsequent research has produced fourth
and Fifth Normal Forms
To have a
consistent & redundant free database, 3rd normal form is
followed. The basic philosophies are to
have
·
No repeating groups (1NF).
·
Every non-key attribute is fully dependent on
primary key (2NF).
·
No transitive dependency among various non-key
attributes (3NF).
§
3.2.3 DATABASE DESIGN:
Deals
with actual organization of data and the access methods
DATABASE DESIGN GUIDELINES :
· Semantics at the attributes i.e. similar type of attributes combine and to form an entity.
· Reducing redundant values in the tuple
· Reducing the null values in the tuple
· Disallowing in generating the spurious tuple.
§
Data Structures (Tables Etc.) of all modules
>> Table:- Item
>> Purpose:- Master
table characterizing the entity raw material
>> Primary Key:- Item_sl_no.
Field Name Constraint Type Size Description Item_sl_ no. Primary
Key Varchar2 40 Item
Serial No. Item_Cate ---do--- 15 Item Category Item_Desc Not
Null ---do--- 50 Item Description Item_type ----do---- ---do--- 25 Type
of item Vendor_Code ----do---- ---do--- 12 Vendor
Code Maint_Status ----do---- Char 1 Maintenance
status Period_From ----do---- Date Period from Period_To ----do---- ---do--- Period to Maint_by ----do---- Char 12 Maintained
by Date_of_Insta ----do---- Date Date
of Installation Waranty/AMC_in_month. Number 10 Period in month User_Code ----do---- ----do---- 5 User code
>> Table:- Vendor
>> Purpose:- Vendor
detail address for further communication
>> Primary Key:- Vendor_code
Field
Name Constraint Type
Size Description Vendor_Code Primary Key Varchar2 5
Vendor code Vendor _Name Not Null ----do---- 25 Vendor name Vendor_Address ----do---- 50 Vendor
address Office_Tel_NO. Number 10 Office
Telephone No Service_Tel_NO. ----do---- 10 Service Telephone No
>> Table:- User
>> Purpose:- User
Details for further communication
>> Primary Key:- User_Code
Field Name Constraint Type Size Description User_Code Primary Key Number 5 User code DDOUnit_Code Varchar2 10 DDO_Location ----do---- 10 User_Name Not Null ----do---- 25 User
name User_Desig. ----do---- ----do---- 10 Designation
of the user. Address ----do---- ----do---- 50 User
address EPABX_Tel_No. Number 10 EPABX Telephone No. Direct_Tel_No ---do--- 10 P&T Telephone No.
>> Table:- Location
>> Purpose:- Location of user
>> Primary Key:- Location_Id.
Field Name Constraint Type Size Description Location_Id. Primary
Key Number 10 Location
identification no. Item_sl_no Not
Null Varchar2 40 Item
serial number Room_No Varchar2 10 Room
number. Floor Not
Null ----do---- 20 Floor
of the particular Bldg. Building Not Null ----do---- 20 Building
name
>> Table:- POrder
>> Purpose:- Details of purchase order.
>> Primary Key:- PO_No
§
3.2.4 SECURITY MEASURES:
·
Data is the most important asset of database systems. To prevent unauthorized access or
manipulation, the user is assigned password to access the system.
·
The maintenance monitoring system monitors all the
activities starting from user’s
maintenance
requisition to report of item. This module is only for the management’s
use. So
different password provision is made for this.
·
The system involves interaction with other databases
viz. Management Info
§
3.2.5 VALIDATION CHECKS
CHAPTER-4
Ø 4.1
PROGRAM STRUCTURE ( HIPO )
§
Number of modules and
its description
The different module can be identified by using HIPO tool. Hierarchical Input Process Output (HIPO) is graphical tool .The basic philosophy is
· What does each module /sub module do?
· How does it work (logic)?
· What are the inputs & outputs?
These features are incorporated through VISUAL TABLE OF CONTENTS (VTOC). It consists of a hierarchy chart that identifies the modules of the system in number and in relation to each other
IT Maintenance
&
Management Information System
( VTOC Chart )
Ø
4.2 FUNCTIONAL DIAGRAM :
GRAPHICAL SYMBOLS USED (in functional diagram ) are description below
>> Module No
:- 1.1
>> Purpose :- Data entry module for Item.
|
INPUT
|
PROCESS
FEATURES 1.Facility for add, edit, save, delete, exit, cancel
options for records. 2. Facility for see first, previous, next, last
record 3.Dropdown list box used for PO_NO & VENDOR_CODE VEDOR_CODE PO_NO |
|
>> Module No
:- 1.2
>> Purpose :- Data entry module for Vender.
|
INPUT
|
PROCESS
FEATURES 1.Vender_Code auto generated. 2.Facility for add, edit, save, delete, exit, cancel
options for records 3. Facility for see the First, previous, next, last
record. |
|
>> Module No
:- 1.3
>> Purpose :- Data entry module for User.
|
INPUT
|
PROCESS
FEATURES 1.USER_Code auto generated. 2.Facilities for add, edit, save, delete, exit, and
cancel options for records 3. Facility for see the First, previous, next, last
record. 4. Dropdown list box used for ITEM_SL_NO from ITEM
database. ITEM_SL_NO |
|
>> Module No
:- 1.4
>> Purpose :- Data entry module for Location.
|
INPUT
|
PROCESS
ITEM_SL_NO USER_CODE FEATURES 1.Facilities for add, edit, save, delete, exit, and
cancel options for records. 2. Facility for see first, previous, next, last
record 3.Dropdown list box used for USER_CODE from USER
database & ITEM_SL_NO from ITEM database |
|
>> Module No
:- 1.5
>> Purpose :- Data entry module for Purchase Order.
|
INPUT
|
PROCESS
FEATURES 1.Facilities for add, edit, save, delete, exit
options for records 2.Facilities for see first, previous, next, last
record |
|
>> Module No
:- 2.1
>> Purpose :- VENDOR WISE INFORMATION FOR ITEM
|
INPUT
|
PROCESS
|
|
>> Module No
:- 2.2
>> Purpose :- USER WISE INFORMATION FOR ITEM
|
INPUT
|
PROCESS
|
|
>> Module No
:- 2.3
>> Purpose :- ITEM WISE PURCHASE ORDER DETAIL
|
INPUT
|
PROCESS
|
|
>> Module No
:- 2.4
>> Purpose :- ITEMS WHICH ARE UNDER WARANTY
|
INPUT
|
PROCESS
LOGIC 1.Select item_sl_no, item_desc, period_to last date of warranty,
vendor_name, vendor_address, off_tel_no, service_tel_no from item, dept where
maint_status=’w’ and vendor_code.vendor = vendor_code.item; |
|
>> Module No
:- 2.5
>> Purpose :- ITEMS WHICH ARE UNDER AMC
|
INPUT
|
PROCESS
LOGIC 1.Select item_sl_no, item_desc, period_to last date of AMC, vendor_name,
vendor_address, off_tel_no, service_tel_no from item, dept where
maint_status=’A’ and vendor_code.vendor = vendor_code.item; |
|
>> Module No
:- 2.6
>> Purpose :- ITEMS FOR WHICH AMC ARE EXPAIRED.
|
INPUT
|
PROCESS
LOGIC 1.Select item_sl_no, item_desc, period_to last date of AMC, vendor_name,
vendor_address, off_tel_no, service_tel_no from item, dept where
maint_status=’A’ and vendor_code.vendor = vendor_code.item; |
|
>> Module No
:- 2.7
>> Purpose :- ITEMS FOR WHICH WARRANTY EXPIRED
|
INPUT
|
PROCESS
LOGIC 1.Select item_sl_no, item_desc, period_to last date of AMC, vendor_name, vendor_address,
off_tel_no, service_tel_no from item, dept where maint_status=’A’ and
vendor_code.vendor = vendor_code.item; |
|
Ø
4.3
CODING :
‘CODING FOR MDI FORM
Private Sub cmd1_Click()
Vendor.Show vbModal
End Sub
Private Sub cmd2_Click()
Item.Show vbModal
End Sub
Private Sub cmd3_Click()
User.Show vbModal
End Sub
Private Sub cmd4_Click()
Location.Show vbModal
End Sub
Private Sub cmd5_Click()
Purchase.Show vbModal
End Sub
Private Sub cmd6_Click()
End
End Sub
Private Sub CmdRep3_Click()
NoAMC.Show vbModal
End Sub
Private Sub CmdRep4_Click()
NoWaranty.Show vbModal
End Sub
Private Sub CmdRep5_Click()
NoAmcWaranty.Show vbModal
End Sub
Private Sub CmdRep6_Click()
PurchaseDet.Show vbModal
End Sub
Private Sub CmdRep7_Click()
UserItem.Show vbModal
End Sub
Private Sub CmdRep8_Click()
VendorItem.Show vbModal
End Sub
Private Sub CmdRep9_Click()
VendorList.Show vbModal
End Sub
Private Sub CmdRp1_Click()
SuppWaranty.Show vbModal
End Sub
Private Sub cmdRp2_Click()
AMCItems.Show vbModal
End Sub
Private Sub M11_Click()
Vendor.Show vbModal
End Sub
Private Sub M12_Click()
Item.Show vbModal
End Sub
Private Sub M13_Click()
Location.Show vbModal
End Sub
Private Sub M14_Click()
User.Show vbModal
End Sub
Private Sub M21_Click()
SuppWaranty.Show vbModal
End Sub
Private Sub M22_Click()
AMCItems.Show vbModal
End Sub
Private Sub M23_Click()
NoAMC.Show vbModal
End Sub
Private Sub M24_Click()
NoWaranty.Show vbModal
End Sub
Private Sub M25_Click()
NoAmcWaranty.Show vbModal
End Sub
Private Sub M26_Click()
PurchaseDet.Show vbModal
End Sub
Private Sub M27_Click()
UserItem.Show vbModal
End Sub
Private Sub M28_Click()
VendorItem.Show vbModal
End Sub
Private Sub M29_Click()
VendorList.Show vbModal
End Sub
Private Sub M3_Click()
End
End Sub
‘CODING FOR ITEM
Dim cn As New ADODB.Connection
Dim RS As New ADODB.Recordset
Dim ven As New ADODB.Recordset
Dim Pord As New ADODB.Recordset
Dim User As New ADODB.Recordset
Dim Adc As Boolean
Private Sub cmdadd_Click()
Adc = True
Deactivate
ItemSlTxt.Text = ""
ItemCatgTxt.Text = ""
ItemDescTxt.Text = ""
ItemTypeTxt.Text = ""
ItemValTxt.Text = ""
UserTxt.Text = ""
ItemSlTxt.SetFocus
End Sub
Private Sub cmdcancel_Click()
If Adc Then
Adc = False
RS.MoveFirst
DD
End If
Activate
End Sub
Private Sub cmddelete_Click()
RS.Delete adAffectCurrent
RS.Update
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub DD()
ItemSlTxt.Text = RS.Fields("item_sl_no")
ItemCatgTxt.Text = RS.Fields("item_cate")
ItemDescTxt.Text = RS.Fields("item_desc")
ItemTypeTxt.Text = RS.Fields("item_type")
ItemValTxt.Text = RS.Fields("item_value")
VenTxt1.Text = RS.Fields("vendor_code")
VendTxt.Text = RS.Fields("maint_by")
DateFrom.Text = RS.Fields("period_from")
DateTo.Text = RS.Fields("period_to")
POTxt.Text = RS.Fields("pono")
UserTxt.Text = RS.Fields("User_Code")
If RS.Fields("maint_status") = "A" Then
Op1.Value = True
ElseIf RS.Fields("maint_status") = "W" Then
Op2.Value = True
Else
Op3.Value = True
End If
End Sub
Private Sub cmdfirst_Click()
RS.MoveFirst
DD
End Sub
Private Sub cmdlast_Click()
RS.MoveLast
DD
End Sub
Private Sub cmdmodify_Click()
Adc = False
ItemSlTxt.SetFocus
Deactivate
End Sub
Private Sub cmdnext_Click()
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdprev_Click()
RS.MovePrevious
If RS.BOF Then RS.MoveFirst
DD
End Sub
Private Sub cmdsave_Click()
If ItemSlTxt.Text = Empty Then
ItemSlTxt.SetFocus
ElseIf ItemCatgTxt.Text = Empty Then
ItemCatgTxt.SetFocus
ElseIf ItemDescTxt.Text = Empty Then
ItemDescTxt.SetFocus
ElseIf ItemTypeTxt.Text = Empty Then
ItemTypeTxt.SetFocus
ElseIf ItemValTxt.Text = Empty Then
ItemValTxt.SetFocus
Else
If Adc Then RS.AddNew
RS.Fields("item_sl_no") = ItemSlTxt.Text
RS.Fields("item_cate") = ItemCatgTxt.Text
RS.Fields("item_desc") = ItemDescTxt.Text
RS.Fields("item_type") = ItemTypeTxt.Text
RS.Fields("item_value") = Val(ItemValTxt.Text)
RS.Fields("vendor_code") = VenTxt1.Text
RS.Fields("maint_by") = VendTxt.Text
RS.Fields("period_from") = DateFrom.Text
RS.Fields("period_to") = DateTo.Text
RS.Fields("pono") = POTxt.Text
RS.Fields("User_Code") = UserTxt.Text
If Op1.Value Then
RS.Fields("maint_status") = "A"
ElseIf Op2.Value Then
RS.Fields("maint_status") = "W"
Else
RS.Fields("maint_status") = "N"
End If
RS.Update
Adc = False
Activate
DD
End If
End Sub
Private Sub Form_Load()
cn.CursorLocation = adUseClient
cn.Open "Dsn=Prasanta", "scott",
"tiger"
RS.Open "Item", cn, adOpenDynamic, adLockOptimistic,
adCmdTable
ven.Open "Vendor", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
Pord.Open "Porder", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
User.Open "user1", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
If Not RS.EOF Then DD
Text9.Text = Date
Label14.Caption = ""
cmdsave.Enabled = False
cmdcancel.Enabled = False
VList.Clear
If ven.EOF Then
MsgBox "No Vendors Data Present. Add Vendor Data
First"
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled = False
cmdexit.Enabled = True
Else
While Not ven.EOF
VList.AddItem (ven.Fields(0))
ven.MoveNext
Wend
VList.Refresh
ven.MoveFirst
End If
VList.Enabled = False
POLst.Clear
If Pord.EOF Then
MsgBox "No Purchases Has been Made."
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled = False
cmdexit.Enabled = True
Else
While Not Pord.EOF
POLst.AddItem (Pord.Fields(0))
Pord.MoveNext
Wend
POLst.Refresh
Pord.MoveFirst
End If
POLst.Enabled = False
UserLst.Clear
If User.EOF Then
MsgBox "No Users Has been Created."
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled =
False
cmdexit.Enabled = True
Else
While Not User.EOF
UserLst.AddItem (User.Fields(0))
User.MoveNext
Wend
UserLst.Refresh
User.MoveFirst
End If
UserLst.Enabled = False
Op1.Enabled = False
Op2.Enabled = False
Op3.Enabled = False
End Sub
Private Sub Form_Unload(Cancel As
Integer)
RS.Close
Pord.Close
ven.Close
User.Close
cn.Close
End Sub
Private Sub POLst_Click()
POTxt.Text = POLst.Text
End Sub
Private Sub Timer1_Timer()
Text10.Text = Time
End Sub
Private Sub Deactivate()
cmddelete.Enabled = False
cmdexit.Enabled = False
cmdfirst.Enabled = False
cmdlast.Enabled = False
cmdprev.Enabled = False
cmdnext.Enabled = False
cmdsave.Enabled = True
cmdcancel.Enabled = True
cmdmodify.Enabled = False
cmdadd.Enabled = False
VList.Enabled = True
POLst.Enabled = True
UserLst.Enabled = True
Op1.Enabled = True
Op2.Enabled = True
Op3.Enabled = True
End Sub
Private Sub Activate()
cmddelete.Enabled = True
cmdexit.Enabled = True
cmdfirst.Enabled = True
cmdlast.Enabled = True
cmdprev.Enabled = True
cmdnext.Enabled = True
cmdadd.Enabled = True
cmdmodify.Enabled = True
cmdsave.Enabled = False
cmdcancel.Enabled = False
VList.Enabled = False
POLst.Enabled = False
UserLst.Enabled = False
Op1.Enabled = False
Op2.Enabled = False
Op3.Enabled = False
End Sub
Private Sub Timer2_Timer()
Static str As String
Static a As Integer
Dim i As Integer
str = "IT EQUIPMENTS - ENTRY FORM"
i = Len(str)
a = a + 1
If a > i Then
a = 1
Label14.Caption = ""
End If
Label14.Caption = Label14.Caption & Mid(str, a, 1)
End Sub
Private Sub UserLst_Click()
UserTxt.Text = UserLst.Text
End Sub
Private Sub VList_Click()
VenTxt1.Text = VList.Text
End Sub
‘CODING FOR VENDOR ENTRY
Dim cn As New ADODB.Connection
Dim RS As New ADODB.Recordset
Dim ven As New ADODB.Recordset
Dim Pord As New ADODB.Recordset
Dim User As New ADODB.Recordset
Dim Adc As Boolean
Private Sub cmdadd_Click()
Adc = True
Deactivate
ItemSlTxt.Text = ""
ItemCatgTxt.Text = ""
ItemDescTxt.Text = ""
ItemTypeTxt.Text = ""
ItemValTxt.Text = ""
UserTxt.Text = ""
ItemSlTxt.SetFocus
End Sub
Private Sub cmdcancel_Click()
If Adc Then
Adc = False
RS.MoveFirst
DD
End If
Activate
End Sub
Private Sub cmddelete_Click()
RS.Delete adAffectCurrent
RS.Update
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub DD()
ItemSlTxt.Text = RS.Fields("item_sl_no")
ItemCatgTxt.Text = RS.Fields("item_cate")
ItemDescTxt.Text = RS.Fields("item_desc")
ItemTypeTxt.Text = RS.Fields("item_type")
ItemValTxt.Text = RS.Fields("item_value")
VenTxt1.Text = RS.Fields("vendor_code")
VendTxt.Text = RS.Fields("maint_by")
DateFrom.Text = RS.Fields("period_from")
DateTo.Text = RS.Fields("period_to")
POTxt.Text = RS.Fields("pono")
UserTxt.Text = RS.Fields("User_Code")
If RS.Fields("maint_status") = "A" Then
Op1.Value = True
ElseIf RS.Fields("maint_status") = "W" Then
Op2.Value = True
Else
Op3.Value = True
End If
End Sub
Private Sub cmdfirst_Click()
RS.MoveFirst
DD
End Sub
Private Sub cmdlast_Click()
RS.MoveLast
DD
End Sub
Private Sub cmdmodify_Click()
Adc = False
ItemSlTxt.SetFocus
Deactivate
End Sub
Private Sub cmdnext_Click()
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdprev_Click()
RS.MovePrevious
If RS.BOF Then RS.MoveFirst
DD
End Sub
Private Sub cmdsave_Click()
If ItemSlTxt.Text = Empty Then
ItemSlTxt.SetFocus
ElseIf ItemCatgTxt.Text = Empty Then
ItemCatgTxt.SetFocus
ElseIf ItemDescTxt.Text = Empty Then
ItemDescTxt.SetFocus
ElseIf ItemTypeTxt.Text = Empty
Then
ItemTypeTxt.SetFocus
ElseIf ItemValTxt.Text = Empty Then
ItemValTxt.SetFocus
Else
If Adc Then RS.AddNew
RS.Fields("item_sl_no") = ItemSlTxt.Text
RS.Fields("item_cate") = ItemCatgTxt.Text
RS.Fields("item_desc") = ItemDescTxt.Text
RS.Fields("item_type") = ItemTypeTxt.Text
RS.Fields("item_value") = Val(ItemValTxt.Text)
RS.Fields("vendor_code") = VenTxt1.Text
RS.Fields("maint_by") = VendTxt.Text
RS.Fields("period_from") = DateFrom.Text
RS.Fields("period_to") = DateTo.Text
RS.Fields("pono") = POTxt.Text
RS.Fields("User_Code") = UserTxt.Text
If Op1.Value Then
RS.Fields("maint_status") = "A"
ElseIf Op2.Value Then
RS.Fields("maint_status") = "W"
Else
RS.Fields("maint_status") = "N"
End If
RS.Update
Adc = False
Activate
DD
End If
End Sub
Private Sub Form_Load()
cn.CursorLocation = adUseClient
cn.Open "Dsn=Prasanta", "scott",
"tiger"
RS.Open "Item", cn, adOpenDynamic, adLockOptimistic,
adCmdTable
ven.Open "Vendor", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
Pord.Open "Porder", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
User.Open "user1", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
If Not RS.EOF Then DD
Text9.Text = Date
Label14.Caption = ""
cmdsave.Enabled = False
cmdcancel.Enabled = False
VList.Clear
If ven.EOF Then
MsgBox "No Vendors Data Present. Add Vendor Data
First"
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled = False
cmdexit.Enabled = True
Else
While Not ven.EOF
VList.AddItem
(ven.Fields(0))
ven.MoveNext
Wend
VList.Refresh
ven.MoveFirst
End If
VList.Enabled = False
POLst.Clear
If Pord.EOF Then
MsgBox "No Purchases Has been Made."
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled = False
cmdexit.Enabled = True
Else
While Not Pord.EOF
POLst.AddItem (Pord.Fields(0))
Pord.MoveNext
Wend
POLst.Refresh
Pord.MoveFirst
End If
POLst.Enabled = False
UserLst.Clear
If User.EOF Then
MsgBox "No Users Has been Created."
Deactivate
cmdsave.Enabled = False
cmdcancel.Enabled = False
cmdexit.Enabled = True
Else
While Not User.EOF
UserLst.AddItem (User.Fields(0))
User.MoveNext
Wend
UserLst.Refresh
User.MoveFirst
End If
UserLst.Enabled = False
Op1.Enabled = False
Op2.Enabled = False
Op3.Enabled = False
End Sub
Private Sub Form_Unload(Cancel As
Integer)
RS.Close
Pord.Close
ven.Close
User.Close
cn.Close
End Sub
Private Sub POLst_Click()
POTxt.Text = POLst.Text
End Sub
Private Sub Timer1_Timer()
Text10.Text = Time
End Sub
Private Sub Deactivate()
cmddelete.Enabled = False
cmdexit.Enabled = False
cmdfirst.Enabled = False
cmdlast.Enabled = False
cmdprev.Enabled = False
cmdnext.Enabled = False
cmdsave.Enabled = True
cmdcancel.Enabled = True
cmdmodify.Enabled = False
cmdadd.Enabled = False
VList.Enabled = True
POLst.Enabled = True
UserLst.Enabled = True
Op1.Enabled = True
Op2.Enabled = True
Op3.Enabled = True
End Sub
Private Sub Activate()
cmddelete.Enabled = True
cmdexit.Enabled = True
cmdfirst.Enabled = True
cmdlast.Enabled = True
cmdprev.Enabled = True
cmdnext.Enabled = True
cmdadd.Enabled = True
cmdmodify.Enabled = True
cmdsave.Enabled = False
cmdcancel.Enabled = False
VList.Enabled = False
POLst.Enabled = False
UserLst.Enabled = False
Op1.Enabled = False
Op2.Enabled = False
Op3.Enabled = False
End Sub
Private Sub Timer2_Timer()
Static str As String
Static a As Integer
Dim i As Integer
str = "IT EQUIPMENTS - ENTRY FORM"
i = Len(str)
a = a + 1
If a > i Then
a = 1
Label14.Caption = ""
End If
Label14.Caption = Label14.Caption & Mid(str, a, 1)
End Sub
Private Sub UserLst_Click()
UserTxt.Text = UserLst.Text
End Sub
Private Sub VList_Click()
VenTxt1.Text = VList.Text
End Sub
‘CODING FOR USER ENTRY
Dim cn As New ADODB.Connection
Dim RS As New ADODB.Recordset
Dim Adc As Boolean
Dim Ucode As Integer
Private Sub cmdadd_Click()
Adc = True
Ucode = Ucode + 1
UcodeTxt.Text = Ucode
DDOTxt.Text = ""
DDOLocTxt.Text = ""
UnameTxt.Text = ""
UdesgTxt.Text = ""
UadrTxt.Text = ""
PbxTxt.Text = ""
TelTxt.Text = ""
Deactivate
UnameTxt.SetFocus
End Sub
Private Sub cmdcancel_Click()
If Adc Then
Adc = False
Ucode = Ucode - 1
RS.MoveFirst
DD
End If
Activate
End Sub
Private Sub cmddelete_Click()
RS.Delete adAffectCurrent
RS.Update
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdexit_Click()
Unload Me
End Sub
Public Sub DD()
UcodeTxt.Text = RS.Fields("user_code")
DDOTxt.Text = RS.Fields("ddounit_code")
DDOLocTxt.Text = RS.Fields("ddo_location")
UnameTxt.Text = RS.Fields("user_name")
UdesgTxt.Text = RS.Fields("user_desig")
UadrTxt.Text = RS.Fields("user_address")
PbxTxt.Text = RS.Fields("epabx_telephone")
TelTxt.Text = RS.Fields("direct_telephone")
End Sub
Private Sub cmdfirst_Click()
RS.MoveFirst
DD
End Sub
Private Sub cmdlast_Click()
RS.MoveLast
DD
End Sub
Private Sub cmdmodify_Click()
Deactivate
Adc = False
UnameTxt.SetFocus
End Sub
Private Sub cmdnext_Click()
RS.MoveNext
If RS.EOF Then RS.MoveLast
DD
End Sub
Private Sub cmdprev_Click()
RS.MovePrevious
If RS.BOF Then RS.MoveFirst
DD
End Sub
Private Sub cmdsave_Click()
If UcodeTxt.Text = Empty Then
UcodeTxt.SetFocus
ElseIf UnameTxt.Text = Empty Then
UnameTxt.SetFocus
ElseIf UadrTxt.Text = Empty Then
UadrTxt.SetFocus
ElseIf UdesgTxt.Text = Empty Then
UdesgTxt.SetFocus
Else
If Adc Then RS.AddNew
RS.Fields("user_code") = UcodeTxt.Text
RS.Fields("ddounit_code") = DDOTxt.Text
RS.Fields("ddo_location") = DDOLocTxt.Text
RS.Fields("user_name") = UnameTxt.Text
RS.Fields("user_desig") = UdesgTxt.Text
RS.Fields("user_address") = UadrTxt.Text
RS.Fields("epabx_telephone") = PbxTxt.Text
RS.Fields("direct_telephone") = TelTxt.Text
RS.Update
Adc = False
Activate
End If
End Sub
Private Sub Form_Load()
cn.CursorLocation = adUseClient
cn.Open "Dsn=Prasanta", "scott",
"tiger"
RS.Open "User1", cn, adOpenDynamic, adLockOptimistic,
adCmdTable
Label14.Caption = ""
If RS.EOF Then
Ucode = 0
Else
RS.MoveLast
Ucode = RS.Fields("user_Code")
RS.MoveFirst
DD
End If
UcodeTxt.Enabled = False
Text9.Text = Date
cmdsave.Enabled = False
cmdcancel.Enabled = False
DD
End Sub
Private Sub Timer1_Timer()
Text10.Text = Time
End Sub
Private Sub Timer2_Timer()
Static str As String
Static a As Integer
Dim i As Integer
str = "USERS OF IT EQUIPMENT - ENTRY FORM"
i = Len(str)
a = a + 1
If a > i Then
a = 1
Label14.Caption = ""
End If
Label14.Caption = Label14.Caption & Mid(str, a, 1)
End Sub
Private Sub Deactivate()
cmddelete.Enabled = False
cmdexit.Enabled = False
cmdfirst.Enabled = False
cmdlast.Enabled = False
cmdprev.Enabled = False
cmdnext.Enabled = False
cmdsave.Enabled = True
cmdcancel.Enabled = True
cmdmodify.Enabled = False
cmdadd.Enabled = False
End Sub
Private Sub Activate()
cmddelete.Enabled = True
cmdexit.Enabled = True
cmdfirst.Enabled = True
cmdlast.Enabled = True
cmdprev.Enabled = True
cmdnext.Enabled = True
cmdadd.Enabled = True
cmdmodify.Enabled = True
cmdsave.Enabled = False
cmdcancel.Enabled = False
End Sub
‘CODING FOR LOCATION ENTRY
Dim cn As New ADODB.Connection
Dim Loc As New ADODB.Recordset
Dim Itm As New ADODB.Recordset
Dim Usr As New ADODB.Recordset
Dim Lid As Integer
Dim Adc As Boolean
Private Sub cmdadd_Click()
Adc = True
Deactivate
Lid = Lid + 1
LocIdTxt.Text = Lid
BldTxt.Text = ""
FlrTxt.Text = ""
RoomTxt.Text = ""
ItemSlTxt.Text = ""
UcodeTxt.Text = ""
ItemNameTxt.Text = ""
UnameTxt.Text = ""
BldTxt.SetFocus
ItemFrm.Enabled = True
UserFrm.Enabled = True
End Sub
Private Sub cmdcancel_Click()
If Adc Then
Adc = False
Lid = Lid - 1
If Lid <> 0 Then Loc.MoveFirst
End If
If Lid <> 0 Then DD
Activate
End Sub
Private Sub cmddelete_Click()
Loc.Delete adAffectCurrent
Loc.Update
Loc.MoveNext
If Loc.EOF Then Loc.MoveLast
DD
End Sub
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub DD()
Usr.MoveFirst
Itm.MoveFirst
LocIdTxt.Text = Loc.Fields("location_id")
BldTxt.Text = Loc.Fields("building")
FlrTxt.Text = Loc.Fields("floor")
RoomTxt.Text = Loc.Fields("room_no")
ItemSlTxt.Text = Loc.Fields("item_sl_no")
UcodeTxt.Text = Loc.Fields("user_id")
Itm.Find "Item_sl_no = '" &
Loc.Fields("item_sl_no") & "'"
Usr.Find "user_code = '" &
Loc.Fields("user_id") & "'"
ItemNameTxt.Text = Itm.Fields("item_desc")
UnameTxt.Text = Usr.Fields("user_name")
End Sub
Private Sub cmdfirst_Click()
Loc.MoveFirst
DD
End Sub
Private Sub cmdlast_Click()
Loc.MoveLast
DD
End Sub
Private Sub cmdmodify_Click()
Adc = False
ItemFrm.Enabled = True
UserFrm.Enabled = True
Deactivate
End Sub
Private Sub cmdnext_Click()
Loc.MoveNext
If Loc.EOF Then Loc.MoveLast
DD
End Sub
Private Sub cmdprev_Click()
Loc.MovePrevious
If Loc.BOF Then Loc.MoveFirst
DD
End Sub
Private Sub cmdsave_Click()
If BldTxt.Text = Empty Then
BldTxt.SetFocus
ElseIf FlrTxt.Text = Empty Then
FlrTxt.SetFocus
ElseIf RoomTxt.Text = Empty Then
RoomTxt.SetFocus
Else
If Adc Then Loc.AddNew
Loc.Fields("location_id") = LocIdTxt
Loc.Fields("building") = BldTxt
Loc.Fields("floor") = FlrTxt
Loc.Fields("room_no") = RoomTxt
Loc.Fields("item_sl_no") = ItemSlTxt
Loc.Fields("user_id") = UcodeTxt
Loc.Update
Adc = False
Activate
DD
End If
End Sub
Private Sub Form_Load()
cn.CursorLocation = adUseClient
cn.Open "dsn=prasanta;uid=scott;pwd=tiger"
Itm.Open "Item", cn, adOpenDynamic, adLockOptimistic,
adCmdTable
Usr.Open "User1", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
Loc.Open "Location", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
Label14.Caption = ""
If Loc.EOF Then
Lid = 0
Else
Loc.MoveLast
Lid = Loc.Fields("Location_Id")
Loc.MoveFirst
DD
End If
Text9.Text = Date
Text10.Text = Time
cmdsave.Enabled = False
cmdcancel.Enabled = False
LocIdTxt.Enabled = False
End Sub
Private Sub Form_Unload(Cancel As
Integer)
Itm.Close
Usr.Close
Loc.Close
cn.Close
End Sub
Private Sub ItemLst_Click()
Itm.MoveFirst
Itm.Find "Item_sl_no = '" & ItemLst.Text &
"'"
ItemNameTxt.Text = Itm.Fields("item_desc")
ItemSlTxt.Text = ItemLst.Text
ItemLbl.Caption = Itm.Fields("item_desc")
End Sub
Private Sub ItemLst_GotFocus()
Itm.MoveFirst
ItemLst.Clear
While Not Itm.EOF
ItemLst.AddItem (Itm.Fields("item_sl_no"))
Itm.MoveNext
Wend
ItemLst.Text = ItemLst.List(0)
ItemLst.Refresh
End Sub
Private Sub Timer1_Timer()
Text10.Text = Time
End Sub
Private Sub Timer2_Timer()
Static str As String
Static a As Integer
Dim i As Integer
str = "User Location - Entry Form"
i = Len(str)
a = a + 1
If a > i Then
a = 1
Label14.Caption = ""
End If
Label14.Caption = Label14.Caption & Mid(str, a, 1)
End Sub
Private Sub Deactivate()
cmddelete.Enabled = False
cmdexit.Enabled = False
cmdfirst.Enabled = False
cmdlast.Enabled = False
cmdprev.Enabled = False
cmdnext.Enabled = False
cmdsave.Enabled = True
cmdcancel.Enabled = True
cmdmodify.Enabled = False
cmdadd.Enabled = False
End Sub
Private Sub Activate()
cmddelete.Enabled = True
cmdexit.Enabled = True
cmdfirst.Enabled = True
cmdlast.Enabled = True
cmdprev.Enabled = True
cmdnext.Enabled = True
cmdadd.Enabled = True
cmdmodify.Enabled = True
cmdsave.Enabled = False
cmdcancel.Enabled = False
End Sub
Private Sub UserLst_Click()
Usr.MoveFirst
Usr.Find "user_code = '" & UserLst.Text &
"'"
UnameTxt.Text = Usr.Fields("user_name")
UcodeTxt.Text = UserLst.Text
UserLbl.Caption = Usr.Fields("user_name")
End Sub
Private Sub UserLst_GotFocus()
Usr.MoveFirst
UserLst.Clear
While Not Usr.EOF
UserLst.AddItem (Usr.Fields("user_code"))
Usr.MoveNext
Wend
UserLst.Text = UserLst.List(0)
UserLst.Refresh
End Sub
‘CODING FOR PURCHASE ORDER
Dim cn As New ADODB.Connection
Dim RS As New ADODB.Recordset
Dim Adc As Boolean
Private Sub cmdadd_Click()
Adc = True
Ponotxt.Text = ""
Valuetxt.Text = ""
Podatetxt.Text = ""
Ponotxt.SetFocus
Deactivate
End Sub
Private Sub cmdcancel_Click()
Activate
RS.MoveFirst
DD
End Sub
Private Sub cmddelete_Click()
RS.Delete
RS.MoveNext
If RS.EOF Then
RS.MoveLast
End If
DD
End Sub
Private Sub cmdexit_Click()
Unload Me
End Sub
Private Sub cmdfirst_Click()
RS.MoveFirst
DD
End Sub
Private Sub cmdlast_Click()
RS.MoveLast
DD
End Sub
Private Sub cmdmodify_Click()
Deactivate
Adc = False
Ponotxt.SetFocus
End Sub
Private Sub cmdnext_Click()
RS.MoveNext
If RS.EOF Then
RS.MoveLast
DD
End Sub
Private Sub cmdprev_Click()
RS.MovePrevious
If RS.BOF Then RS.MoveFirst
DD
End Sub
Private Sub cmdsave_Click()
If Ponotxt.Text = Empty Then
Ponotxt.SetFocus
ElseIf Valuetxt.Text = Empty Then
Valuetxt.SetFocus
ElseIf Podatetxt.Text = Empty Then
Podatetxt.SetFocus
Else
If Adc Then RS.AddNew
RS("pono") = Ponotxt.Text
RS("value") = Val(Valuetxt.Text)
RS("podate") = Podatetxt.Text
RS.Update
Activate
Adc = False
DD
End If
End Sub
Private Sub Form_Load()
cn.CursorLocation = adUseClient
cn.Open "dsn=prasanta;uid=scott;pwd=tiger"
RS.Open "porder", cn, adOpenDynamic,
adLockOptimistic, adCmdTable
Text9.Text = Date
Text10.Text = Time
cmdsave.Enabled = False
cmdcancel.Enabled = False
Adc = False
If RS.EOF Then
Ponotxt.Text = ""
Valuetxt.Text = 0
Podatetxt.Text = ""
Else
RS.MoveFirst
DD
End If
End Sub
Public Sub DD()
Ponotxt.Text = RS.Fields("PONO")
Valuetxt.Text = RS.Fields("VALUE")
Podatetxt.Text = RS.Fields("PODATE")
End Sub
Private Sub Form_Unload(Cancel As
Integer)
RS.Close
cn.Close
End Sub
Private Sub Podatetxt_GotFocus()
mSGlBL.Caption = "Enter Date of Purchsing the Items"
End Sub
Private Sub
Podatetxt_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
If Podatetxt.Text = Empty Then
Podatetxt.SetFocus
Else
cmdsave.SetFocus
End If
End If
End Sub
Private Sub Ponotxt_GotFocus()
mSGlBL.Caption = "Enter Purchase Order Number"
End Sub
Private Sub
Ponotxt_KeyPress(KeyAscii As Integer)
If KeyAscii = 13 Then
If Ponotxt.Text = Empty Then
Ponotxt.SetFocus
Else
RS.MoveFirst
RS.Find "pono = '" & Ponotxt.Text &
"'"
If RS.EOF Then
Valuetxt.SetFocus
Else
MsgBox "Duplicate Purchase Order No"
Ponotxt.Text = ""
Ponotxt.SetFocus
End If
End If
End If
End Sub
Private Sub Timer2_Timer()
Static str As String
Static a As Integer
Dim i As Integer
str = "PURCHASE ORDER ENTRY FORM"
i = Len(str)
a = a + 1
If a > i Then
a = 1
Label14.Caption = ""
End If
Label14.Caption = Label14.Caption & Mid(str, a, 1)
End Sub
Private Sub Deactivate()
cmddelete.Enabled = False
cmdexit.Enabled = False
cmdfirst.Enabled = False
cmdlast.Enabled = False
cmdprev.Enabled = False
cmdnext.Enabled = False
cmdsave.Enabled = True
cmdcancel.Enabled = True
cmdmodify.Enabled = False
cmdadd.Enabled = False
End Sub
Private Sub Activate()
cmddelete.Enabled = True
cmdexit.Enabled = True
cmdfirst.Enabled = True
cmdlast.Enabled = True
cmdprev.Enabled = True
cmdnext.Enabled = True
cmdadd.Enabled = True
cmdmodify.Enabled = True
cmdsave.Enabled = False
cmdcancel.Enabled = False
End Sub
Private Sub Timer1_Timer()
Text10.Text = Time
End Sub
Private Sub Valuetxt_GotFocus()
mSGlBL.Caption = "Enter Total Value of the Purchased
Items"
End Sub
Private Sub Valuetxt_KeyPress(KeyAscii
As Integer)
If KeyAscii = 13 Then
If Val(Valuetxt.Text) <> 0 Then
Podatetxt.SetFocus
Else
Valuetxt.SetFocus
End If
End If
End Sub
CHAPTER-5
Ø
v
5.0 TESTING:
Testing
is a process of executing a program with the intent of finding an error. A good
test case is one that has a high probability of finding an as-yet undiscovered
error. A successful test is one that uncovers as-yet undiscovered error.
Testing Principles :
Before applying
methods to design effective test cases, a software engineer must understand the
basic principles that guide software testing.
The
principles are:
·
All tests should traceable to customer requirements.
·
Tests should be planned long before testing begins.
·
The Parto principle applies to software testing.
·
Exhaustive testing is not possible.
Ø Unit Test :
Tests
each low level business process. In the Unit test the basic functionality of
each low level process our system. Keeping this Scenario in mind the goal of
the unit test is to correct the scripts according to the requirements of the
project.
This is
done by using two approaches.
·
Testing the code logic
·
Examining the functional specifications
After all
low level units are identified, tested and approved by our project guide and it
is time to assemble all pieces of the application and begin the next phase of
the testing e.i. system testing.
Ø
Code Testing :-
Here
dummy data are keyed in and executed to ensure correctness of each instruction in
a module,
Ø
Testing by the group leader
The basic aim behind this is to discover any unseen error.
·
Testing
with live data
Live data was collected from the existing system and entered into the
new system for testing .
·
Testing by
Users
Test data
was fed by the users of the system . Then the system is tested for all its
operations . Reports are generated and the print-outs are checked against the
data entered . Reports are also compared with the reports of the existing
system .
Ø Result:-
The users
views against the operation of the system were carefully noted and changes are
made whenever necessary .After all low level units are identified, tested and
approved by our project guide and it is time to assemble all pieces of the
application and begin the next phase of the testing e.i. system testing.
Ø System test:
Test each Unit as a Whole entity/object. The system test combines all units of the application .It is essential that at list one or two end users be involved in the system test to ensure the no requirement has been left out of the applications. The system test ensures that navigation through system is consistent and is maintained the applications provides the flexibility and components the user has requested. During this the integration of each module is tested. Here the main concern was the compatibility of the individual modules. Method followed :-
Artificial
test data are created to test all combination of formats and values the
front-end Power builder 6.0 is based on object oriented technology so the error
regarding interaction of different modules is less and if any, are reported
during compilation.
Ø Integration
test:
Test
whether applications runs with all component of the applications. An important
part of the integration test is running the application on users workstations
Another portions of integration test is to make sure that application executes
and integrates with other GRIDCO departments.
Ø Volume
Test:
Test whether
the applications are maintained production volume of data and stay within
acceptable time limit.
Ø Acceptance Test:
Test
continuously throughout all stages of the all-testing process to determine
whether the end user approves of the design and functionality of the system.
Ø
WHITE-BOX TESTING:
White box
testing, some times called glass box testing is a test case design method that
used the control structures of the procedural design to derive test cases.
·
Guarantee that independent path within a module have been
exercised at least once.
·
Exercise all logical decision on their true and false
sides.
·
Execute all loops at their boundaries and within their
operational bounds.
·
Exercise internal data structures to assure their validity.
Ø BLACK-BOX
TESTING:
It focuses on the functional requirements of the
software and it enables the software engineer to derive set of input conditions
that will fully exercise all functional requirements for a system.
When computer software is considered, black-box testing
alludes to test that are conducted at the s/w interface. They are designed to
uncover errors it tests are used to demonstrate that s/w functions are
operational.
Ø VALIDATION TESTING:
Validation
can be defined as when s/w functions in a manner that can be reasonable
expected by the customer.
Software
validation is achieved through a series of black box tests that demonstrates
conformity with requirements after each validation tests case has been
conducted; one of the two possible conditions exists.
The function or performance characteristics conform to specification is
accepted.
A
deviation from specification is uncovered and a deficiency list is crated.
§
ALPHA TESTING:
The alpha test is conducted at the developer’s
site by customer. The software is used in a natural setting with the developer
“ looking over the shoulder “ of the user and recording errors and usage
problems. Alpha tests are conducted in a controlled environment.
§
BETA TESTING
The beta
test is conducted at one or more customer sides by end users of the soft wares.
Unlike alpha testing, the developer
is generally not present. Therefore, the beta test is a “ live” application of
the software in an environment that cannot be controlled by the developer. The
customer records all problems (real or imagined) that are encountered during
beta testing and reports these to the developer at regular intervals .As a
result of problems reported during beta test, the software developer makes modifications
and then prepared for release of the soft ware products to the entire customer
case.
Ø IMPLEMENTATION AND EVALUATION:
Implementation involves the
activities that take place to convert from old system to new. During this
system has undergone the following steps:
Ø TRAINING
·
A user manual is made and given to the users for ready
reference where all screen and their operating procedures are explained with
examples.
·
User training is organized.
·
User used the system with live data.
Ø CONVERSION
Conversion is a process of changing from the old system to the new one . We have adopted the parallel conversion method as the cost of running a parallel system were not high and were affordable . Now the system is operational simultaneously with the previous system.
Ø
POST
IMPLEMENTATION REVIEW
After the
system was implemented and the conversion was completed, a review of the system
was conducted. It was found that the operating costs were reduced and the speed
of operation was increased. The system is giving the accurate and timely
information. There is a complete control over the data. This system reduced the
efforts and time. The system has achieved all its objectives. All the users of
the systems are satisfied with the new system
CHAPTER-6
Ø
DOCUMENTATION:-
STEP 1
Enter the
log in and password
STEP 2
Main Screen
1. Main screen contains items
like Data entry, Report and exit
2.
As the name suggests these have dropdown submenu items.
3. And
also the different command buttons are available in the screen for different
items
4. Click the
item in which you want to work with.
STEP 3
DATA ENTRY SCREEN FOR VENDOR
¨ The screen provides the following functionality
·
In the screen the ‘save’ & ‘Cancel’ button are disable.
·
While Click on the ‘Add’ button all the buttons are disable
except ‘Save’ & ‘Cancel”.
·
Vendor code is auto generated.
·
Click on the ‘Save’ button, it will save the data with the
previous data.
·
Click on the ‘Cancel’ button, it will cancel the execution.
·
Click on the ‘Exit’ button, it will terminate the
application.
·
Click on the ‘<<’ button, it will show the first
record.
·
Click on the ‘<’ button, it will show the previous
record.
·
Click on the ‘>>’ button, it will show the last
record.
·
Click on the ‘>’ button, it will show the next record.
DATA ENTRY
SCREEN FOR ITEM.
¨ The screen provides the following functionality
·
In the screen the ‘save’
‘Cancel’ & Maintenance Status button are disable.
·
While Click on the ‘Add’ button all the buttons are disable
except ‘Save’ , ‘Cancel’ & Maintenance status.
·
Click on the ‘Save’ button, it will save the data with the
previous data.
·
Click on the ‘Cancel’ button, it will cancel the execution.
·
Click on the ‘Exit’ button, it will terminate the
application.
·
Click on the ‘<<’ button, it will show the first record.
·
Click on the ‘<’ button, it will show the previous
record.
·
Click on the ‘>>’ button, it will show the last
record.
·
Click on the ‘>’ button, it will show the next record.
·
Select the appropriate ‘Vendor_Code’ & ‘PONO’ from
Vendor Code & ‘Purchase order no’
help drop down list box.
DATA ENTRY SCREEN FOR USER OF IT EQUIPMENT.
¨ The screen provides the following functionality
·
In the screen the ‘save’ & ‘Cancel’ button are disable.
·
While Click on the ‘Add’ button all the buttons are disable
except ‘Save’ & ‘Cancel”.
·
User code is auto generated.
·
Click on the ‘Save’ button, it will save the data with the
previous data.
·
Click on the ‘Cancel’ button, it will cancel the execution.
·
Click on the ‘Exit’ button, it will terminate the
application.
·
Click on the ‘<<’ button, it will show the first
record.
·
Click on the ‘<’ button, it will show the previous
record.
·
Click on the ‘>>’ button, it will show the last
record.
·
Click on the ‘>’ button, it will show the next record.
DATA ENTRY SCREEN FOR USER OF IT EQUIPMENT.
¨ The screen provides the following functionality
·
In the screen the ‘save’ & ‘Cancel’ button are disable.
·
While Click on the ‘Add’ button all the buttons are disable
except ‘Save’ & ‘Cancel’
·
Click on the ‘Save’ button, it will save the data with the
previous data.
·
Click on the ‘Cancel’ button, it will cancel the execution.
·
Click on the ‘Exit’ button, it will terminate the
application.
·
Click on the ‘<<’ button, it will show the first
record.
·
Click on the ‘<’ button, it will show the previous
record.
·
Click on the ‘>>’ button, it will show the last
record.
·
Click on the ‘>’ button, it will show the next record.
·
Select the appropriate ‘Item_sl_no’ & ‘User_code’ from
‘Item serial no’ & ‘User code’ help drop down list box.
DATA ENTRY SCREEN FOR PURCHASE ORDER
¨ The screen provides the following functionality
·
In the screen the ‘save’ & ‘Cancel’ button are disable.
·
While Click on the ‘Add’ button all the buttons are disable
except ‘Save’ & ‘Cancel”.
·
Click on the ‘Save’ button, it will save the data with the
previous data.
·
Click on the ‘Cancel’ button, it will cancel the execution.
·
Click on the ‘Exit’ button, it will terminate the
application.
·
Click on the ‘<<’ button, it will show the first
record.
·
Click on the ‘<’ button, it will show the previous
record.
·
Click on the ‘>>’ button, it will show the last
record.
·
Click on the ‘>’ button, it will show the next record.
CHAPTER –7
In the present world
‘change’ is the only thing that dose not change. Homo Sapiens are known for
their adaptability and that is the very reason why human race survives millions
of years of hazardous and diverse natural conditions. But there will be strong
adverse currents against any change contemplated and, as the euphoria dies
down, people gradually starts appreciating the benefits they derive out the new
system.
With limited knowledge and limited time, it is
really not an easy task to come out with “complete and perfect” software.
Despite the best effort within academically constrained project duration, the
developed system may suffer certain limitations, and, therefore, will have
certain scope for its further improvement. To mention a few, in the future
study:
·
The system can be
upgraded to run in the Internet networking environment, which will be of
tremendous help for on-line monitoring.
·
This system shall be merged
with organization’s overall inventory control and management system. The
interface provided in the system allows smooth integration of the system with
maintenance monitoring system in future
CHAPTER-8
·
Software Engineering A Practitioner’s Approach
Fourth edition
Groge S. Pressman
McGRAW-Hill Publishing Company.N.Y.
International Editions 1997
·
An Integrated Approach To Software Engineering
Second edition
Pankaj Jalote
Narosa Publication.1998
·
System Analysis And Designing Second
Edition
Elias M Awad
Galgotia Publication.1996
·
Operating Systems Second Edition
Milan Milenkovi’c
Tata McGRAW-Hill Publishing Company.
New Delhi 1997
·
Database System Concepts Second Edition
Henry f. Korth
Abraham silberschatz
McGRAW-Hill Publishing Company. N.Y.
International Edition 1991
·
An Introduction To Database System
Bipin C. Desai
Galgotia Publication. 1999
·
An Introduction To Database Systems Third Edition
C.J Date
Narosa Publishing house. 1999
·
Visual Basic 6.0
Paul Sheriff
Prentic Hall Of India. 1999
·
Visual Basic 6.0
By Gary Cornell
Tata Mcgraw-Hill Publishing Company.
·
Visual Basic 6 client/server How-To
By Noel Jerke, George Szabo, David
Jung, & Don Kiely
The Waite Group’s,Techmedia Sams
Publication. 1999
·
Peter Norton’s Guide To Visual Basic 6
By Peter Norton And Michel Groh
Techmedia Sams Publication. 1998