Você está na página 1de 127

PROJECT PROFILE

 Project Title :Metal Firm Management System

 Objective : The main objective of the computerization of the


entire manual office process is to have a quick and easy access to data which
deals with employee pay slip generation, handling customer orders, supplier
purchases, loan management and maintaining an inventory and managing
the finances of the organization. This helps the in the management and
competent functioning of any company.

 Company : Ram Sai Ultra Services

 Operating System : Microsoft Windows 2000/XP

 RDBMS : Microsoft Access 2007

 Front End Used : Microsoft Visual Basic 6.0

 Project Duration : July 2009 – March 2010

 Submitted By : Mr.Pratik Mehta

: Mr Tejas Pandya

 Submitted To : Usha Pravin Gandhi College of Management,

Mumbai University.

1
ACKNOWLEDGEMENT

The preceding material is a sincere effort from my side to create the


“Ram Sai Ultra Services Company” software as my B.Sc.[I.T.] Project.

I extend my heartfelt gratitude to Prof. Smriti Nanavati (H.O.D) for


her valuable co-operation. We are highly obliged to Prof. Mudassar Qureshi,
Prof. Swapnali Londhe and Prof.Shailja Shah for being the guiding stars in
achieving our goal. Without their valuable guidance, expertise and their kind
attention, this project report would not have seen the light of day.

I am also indebted to the lab assistant Mr. Jagdish for his technical support. I
express my warm wishes to the staff members for their assistance & kind guidance
who helped me out of all my queries.

Finally, thanks to my family & friends for their patience & support during
the long run of this project. This project has imparted in me to a great deal of
practical experience, which will prove to be helpful in the near future.

Pratik Mehta

Tejas Pandya

2
PREFACE

It gives me great pleasure to present the project on “METAL


FIRM MANAGEMENT SYSTEM” prepared sincerely, punctually and with
utmost efforts.

The contents of this book are presented into many chapters, in


order to ease reading. Wherever possible the contents are well explained. The
project has been illustrated with precise data elucidated with neat dataflow
diagram, Entity-Relationship diagram and structure diagram that simplify in
understanding the software. The project includes the software development tools
like VB, data reports to present the software very precisely.

Meticulous care has been taken to make this project perfect, useful
and simple in every respect possible.

3
TABLE OF CONTENTS

1. Introduction

1.1 Introduction of the Company

1.2 Existing Manual System

1.3 Proposed System

1.3.1 Features of proposed system

2 System Requirements

2.1 Product Definition

2.2 Feasibility Study

2.3 Processing environment

2.3.1 Hardware requirements

2.3.2 Software requirements

3 Project Plan

3.1 Fact Finding Techniques

3.2 Programing language and development tools

4
4 Design Document

4.1 Data Flow Diagram

4.2 Structured Chart

4.3 Entity Relationship Diagram

4.4 Gantt Chart

5 Data Dictionary

5.1 Data Dictionary

5.2 Data Base Description

6 Architectural Design

6 .1 Screen Layouts & Reports

6.2 Coding Details

7 System Implementation & Testing

8 Conclusion

9 Bibliography

5
Chapter 1

INTRODUCTION

6
INTRODUCTION
Organization Profile : RAM SAI ULTRA SERVICES is an exciting, fast
growing company having an aggressive approach to innovation and sophisticated
processes. Specifically Company’s business is to help its Customers with a wide
range of quality goods at the most competitive rates. It currently deals in non-
destructive testing like ultra sonic test.

Name: RAM SAI ULTRA SERVICES

Proprietor: Mr Nitin Pandya (Owner and Founder of RAM SAI ULTRA


SERVICES.)

Mobile no : 9324212787 / 26112787

Address: 12,Maheshwari bldg, Kankuwadi, PM road, Vile parle (East).Mumbai


400057

Product Profile:
A Metal Firm Management System is being developed for RAM SAI ULTRA
SERVICES for internal use.

7
COMPANY PROFILE
The Metal Firm Management System Application is developed for Ram Sai Ultra
Services. It is Located at kalamboli, Navi Mumbai. A well known firm dealing in
non-destructive testing of various types of materials. It was established in 1995 on
a very scale and since then it has expanded into a huge service center.

Ram Sai Ultra Services has its client based basically in Mumbai and many major
cities in India. The organization offers wide variety of service suiting to different
customers based on their locations keeping in mind the economical costing.

Their motto is to provide best possible services with utmost satisfaction of the
customer and enable them to make best decisions. Apart from the Head Office at
kalamboli, another office is located in the affluent suburbs of Vile Parle,Mumbai.

Their reputation demands the maintenance of the vast product portfolio, segmented
into specialists range and their vision to provide better customer satisfaction.

The “Integrated Office Management” is developed in a generalized way but the


norms are taken from this company and I had gone through the rules and regulation
of the company and noticed that it had a great order processing department along
with an efficient supplier purchasing department .

The company is now going to automate all its departments and they are going to
implement Metal Firm Management Software in their company.

8
SCOPE

 It is specifically designed for the internal use of the company.

 It is specifically designed to automate the existing manual system of


the company.

 It is internal to the Company and hence will not be available to clients


or staff from outside the Company.

 It is a system that deals with :

 Employee Personal Details and Salary.


 Customer Order Processing.
 Supplier Purchase Processing.
 Inventory Management.

9
OBJECTIVE

 To automate the current manual system of the Company.

 Create a flexible system by developing software in place of the


manual system.

 To create reports that will automatically generated as per the required


data of the user of the software.

 Develop a system to manage the internal process of the Company in


a cost effective manner.

 Help you to maintain better database of the system and avoiding the
headache for the owner and the person dealing with the database
management of the system.

10
EXISTING MANUAL SYSTEM

Existing system is based on manual work and all the process are done manually, so
they maintain registers and files for recording all the details of the system.

Introduction

Company Management takes active role in the modern economic scenario of


any country. The abundant resources alone cannot benefit the growth of the
country without managing need and supply. In fact, the difference is in quality
management and utilization of the resources.

Out of the fundamental areas of management, management is adjudged as


the most important area. The concept of management is increasingly becoming a
most vital function of a modern manager.

Management

The total knowledge, skills, creative, abilities, talents & aptitudes of


Companys workforce to capture clients and satisfy their needs along with value
added services is the need of the hour. An Company success depends on how well
they manage their customers and their orders with the proper co-ordination with
supplier and the convenience of payment from the client/customer and the supplier.

The Company is partially computerized. The use of computer is only for


preparing the reports by typing it as needed. The Company has maintained
different registers such as Customer detail and Company Stock detail register,
Loan maintenance register, etc.

11
12
DRAWBACKS OF EXISTING SYSTEM

The phase of system analysis process deals with problems which are
affecting in the current manual system. The problems are those which are affecting
the Company in its daily routine work.

As the growing trend , need of accuracy, perfectness, speed and high memory data
storage is a must. Each and every problem must be solved with a least amount of
time and energy.

The problems faced by existing system are described as below:

 Difficulty in Maintenance of Records.

 Time Consuming.

 Editing of data becomes a tedious job.

 No Security of Data.

 Mistakes Occurring in long

 Lack of Efficiency and Man Power.

 High Data Redundancy.

 Data Inconsistency.

13
 Difficulty in Maintenance of Records :

It is very difficult to maintain data record in the system as all the records
are entered in the register or the respective record books. There are chances of the
record books or files in which all the data is kept may be torn or wearied out or
some other damages which results in the destroyed data. Also a problem occurs if
the data file or register is misplaced somewhere else and is not getting at the time
of actual requirement of the data stored. It is also difficult to maintain old files and
registers which have data of past years which the Company has kept for future
references.

 Time Consuming :

It is very time consuming process to write each and every entry in the
database register. Also it takes a lot of time if all the entries are repeated. In the
system processes such as making different type of reports, billing, prescription
generation and tedious calculations are examples of time consuming process in the
system. It is also time consuming process to know the total number of bills
generated and the payment to each distributor and the payment made by the patient
i.e. to know the status of any Company is very difficult to know, when written
manually but through computerized system it takes less time as it is speedy and
accurate.

 Editing of Data:

Manual written data cannot be changed or edited once written. If there is a mistake
and if we try to rub and write it again it makes the register very dirty and untidy,
which creates a bad impression of the business. If data is entered incorrect whole

14
document gets incorrect while editing wrongly entered data cannot easily solve
errors.

If one had done some wrong entry then to edit the data one has to go through lots
of records and, again and again editing the record makes it difficult to read.

 Data Insecurity :

As the data is stored in files or registers, it is not in a secure place. As the


storage media here are files and books or registers there are chances of getting
these storage media lost, torn, or it may go in the hand of wrong person, which can
destroy the database, or it can also be destroyed accidentally. Also in the system
data should be shown to the person according to his position and post in the
Company, everybody should not be allowed to use all the data. If the data goes in
the hand of wrong person then he/she may take the advantage of the data. So
security is the major aspects of the Company Management System.

 Report Generation :

As Company deals with the Patients and Suppliers so it requires many


types of reports, so it becomes very tedious for the receptionist of the Company to
check all the respected date and data, and according to the data creating respective
reports for the transactions. A computerized system having report making facility
can do this job easily and Company can draw different types of charts and
diagrams to make it understand the ups and downs of his value as well as market.

 High Data Redundancy:

As mentioned in the current system, due to maintenance of so many registers there


is a high redundancy of data i.e. same data is recorded repeatedly.

15
 Data Inconsistency:

Here as mentioned in the above step the same information is written in more than
one place that creates the problem, when there is a change or deletion in the
recorded data.

16
FACT FINDING TECHNIQUES

 Information gathering in any Company is not an easy task.


 It has to be gathered in an organized way so that :
(a) No system details are left out.

(b) Right problems are identified.

(c) Repetitive work is avoided.

(d) Wrong or incomplete details are not collected.

 To do this, a proper search strategy must be decided first, search strategy


includes selecting information sources and search methods.
 It also includes modeling methods to make sense out of information so
collected.
 Here an overall idea about the search methods or fact gathering techniques
which are used while gathering the information, they are:
(1) Interviewing.

(2) Record inspection.

(3) Observation.

 These techniques are used in system analysis and design stage.


I have visited many times at the Company to get information as well as the basic
problems which are occurring in the current existing manual system. As each and

17
every person in the Company has different types of job to be done so we met some
of the people of the Company.

(1) Interviews:
 Interview allows the analyst to collect or gather the information from the
individual or group who are generally the current user of the existing system or
potential user of the proposed system.
 They may be managers or employee of the firm itself who provide the data for
the proposed system and who will be affected by it.
 As far as interview is concerned, it is a time consuming process.
 It is a basic source of qualitative information.
 It allows the analyst to discover areas of misunderstanding, indication of
resistance to the proposed system. An Interview could be :

(1) Structured:

Here, it uses standardized questions as far as response of the questions is


concerned; they are divided into two formats:

(a) Open response format:

Here the questions are answered in ones own words.

(b) Closed response format:

Here set of prescribed answers are used.

(2) Unstructured:

Here the questions are worded to suit the respondent that provide the
information about the areas overlooked or not thought to be important.

18
 Advantages and Disadvantages of structured and unstructured
interviewing:

 Advantages:

(1) Structured:

 Ensures uniform wording of questions to all respondents.


 Easy to administer and evaluate.
 Less interview training required.
 Result in shorter time.

(2) Unstructured:

 Questions can be worded to suit the respondent.


 May produce the information about the areas overlooked or not thought to be
important.

 Disadvantages:

(1) Structured:

 Cost of preparation is high.


 Such high level of structure may not always be suitable.
 Some respondent may resist to such structure.

19
(2) Unstructured:

 Inefficient use of interviewer and respondent time.


 Results take a longer time.
 Extra time required for the collection of essential facts.
 The success of the interview depends on the skill of the interviewer and
his/her preparation for the interview.
 Analysts must also be aware of the kinds of difficulties at some interview, and
must know how to deal with the potential problems.

User interviews were conducted to determine the qualitative information. These


interviews which were unstructured interviews provided opportunity to gathered
information from respondents who are involved in the process for a long time.

These interviews provided information such as:

 Activities involved in the customer ordering process.

 Steps in loan monitoring.

 Activities involved in the purchase orders.


 Limitation of existing system.
 Problems faced by the user in the existing system.

20
(2) Record Review:

 It is said to better believe in records than in people.


 Thus a good analyst always gets facts from documents.
 An existing system can be better understood by examining existing documents,
forms and files.
 In record review analyst examine information that has been recorded about the
system and users.
 Records inspection can be performed at the beginning of study as an
introduction or later in study as a basis for comparing actual operations with
what the records indicate should be happening.
 Records may include:
1) Written policy manuals.

2) Rules and regulations.

3) Standard operating procedures used in the system

4) Forms and documents.

 A good documentation system provides relationships and interaction between


them.
 Analyst also can know about system structures, activities, procedures and flow
of data.
 Records do not show how tasks are performed or what activities are actually
occurring and where decision making power lies.

21
 Analyst through good analysis can get answers to questions like:
1) Who uses the forms?

2) Do they include all necessary information?

3) How readable and easy to follow is the records?

4) Is it ideal for analysis and inferences? Etc.

To gather details about the system, many kinds of records and reports were
reviewed. The study covered.

 Standard operating procedure


 Reports generated by the existing system.
 Document flow (input/output).
 Process of checking stocks manually.
 Process storing the product information.
 Process of keeping track of detailed information.
 Types and format of database registers.

22
(3) Observation:

 Observation can bring in missed facts, new ways to improve the existing
procedures, duplicate work done inadvertently, etc.
 Observation can bring in what other fact-finding methods cannot! But this task
is delicate because people do not like to be observed when they work.
 It is not the quantity of time observed is important but the unorthodox angles of
observation of the work content and methods are going to be rewarding.
 Observation gives analyst the opportunity to go behind the scenes in a system to
learn inside story to discover how things work in new areas of information.
 Observation can look for:
(a) Operational inefficiencies.

(b) Alternate routes and procedures.

(c) Interruptions in the normal flow of work.

(d) The usage of files and documents.

(e) Informal communication channels, etc.

 On site observation provides close view of the working of the real system.
 One can observe people, objects, documents and occurrences of events.

23
PROPOSED SYSTEM

The manual system of the Organization as “Office Management System” is


to be computerized in order to overcome the problems, which affects the existing
manual system. Computerizing the existing system with the help of some
programming language, database package ease the work of the system up to a great
extent.

Generally there has been a criterion to work on any job or task for a specific
purpose. Nobody works without specific detailed information about the particular
task he is performing. Thus, any transaction can be performed either registering a
customer or preparing the pay slip of any employee, etc. In the computerized
system, the first screen of the system would be a welcome message and a list of
menus. These menus contain the options of either entering the details of the
Customer, Supplier or the Employee or starting an transaction by placing an order
with the supplier or checking availability of stock or registering a loan and its
subsequent installments.

After the transaction is completed the user can log off from the system by
simply quitting from the system.

24
FEATURES OF THE PROPOSED SYSTEM
1. This software is very co-operative with the users and more of user-friendly
nature.

2. The system is being developed in MS Access 2007 as backend and VB6.0 as


front end.

3. For security purpose there is password facility and unless we give this
password we cannot open or create entry.

4. System generates code for each user, patient, appointment, order, service etc,
to avoid inconsistency of data.

5. It uses a normalized data structure minimizing redundancy & inconsistencies


to large extent.

6. Automation of various calculation & formulations, for very quick & less
time consuming reports.

7. It is reliable since formulations are computerized and present validation


checks leads to error free results.

8. Better performance in certain jobs.

9. Developing the value system around competition.

25
Chapter 2

SYSTEM
REQUIREMENTS

26
PRODUCT DEFINITION
Metal Firm Management System deals with Product and Distributors. Thus our
product keeps track of all the transactions being held in the before, after and during
the Service and Purchase process.

FUNCTIONS TO BE PROVIDED

The functions provided by this system are:

a. Security

The system is secured in the sense that a transaction is valid only when a
higher authority authenticates it.

b. Registration

The system allows storage of details of Employes , Supplier , Customer etc

c. Information Transaction

Any User when he/she is appointed is given a right, thus according to his/her
right he/she can perform the transactions but is not allowed to view, modify or
delete any other employee.

d. Generation of Reports

The reports can be generated at any moment of time by just a click of the
button.

27
FEASIBILITY STUDY
A feasibility study is undertaken to determine the possibility or
probability of either improving the existing system or developing a completely new
system. It helps to obtain an overview of the problem and to get rough assessment
of whether feasible solution exists. This is essential to avoid committing large
resources to a project and then repent on it later.

To fulfill the requirement of the Company, acceptance criteria are needed.


The user specifies all the needs that they want in their system by giving necessary
data. When the developer develops the system he has to take all points into
consideration and proceed accordingly. Once, when the system is completed the
developer needs to check whether it fulfills the criteria of the user. If it is fulfilled
then the user accepts the system. This acceptance criterion depends not only on the
designing but also the study of feasibility. So it is necessary to study the feasibility
of the system. Feasibility study is to determine whether the solution is feasible
(achievable).

 Need for Feasibility Study


The feasibility study is needed to:

(1) Answer the question whether a new system is to be installed or not?


(2) Determine the potential of the existing system.
(3) Improve the existing system.
(4) Know what should be embedded in the new system.
(5) Define the problems and objective involved in a project.
(6) Avoid costly repairs at a later stage when the system is implemented.

28
(7) Avoid crash implementation of a new system.
(8) Avoid the ‘Hardware Approach’ i.e. getting a computer first and then
deciding how to use it.

There are three aspects in feasibility study portion of the


preliminary investigation. They are:

(1) Technical feasibility.


(2) Economic feasibility and
(3) Operational feasibility of the project.

(1) Technical Feasibility


 Technical Feasibility determines whether the work for the project be done with
the present equipment, current procedures, existing software’s technology and
available personnel?
 If new technology is needed then what alternatives will be needed in the present
structure and work ethos?
 This will require a close examination of the present system.
 The technical feasibility should ask questions related to:
1) Adequacy of available technology.
2) Adequacy of hardware.
3) Available of computer.
4) Operating time and support facilities, etc.

Technical feasibility determines whether the technology needed for the


proposed system is available and how it can be integrated within the system and

29
Technical evaluation must also assess whether the existing system can be
upgraded to use the new technology.

The technical feasibility in the proposed system deals with the technology
used in the system. It deals with the hardware and software used in the system
whether they are of latest technology or not. It happens that after a system is
prepared a new technology arises and the user wants the system based on that
technology. Thus it is important to check the system to be technically feasible.

The minimum memory requirement is 32MB of RAM while 64MB is better


to have for better performance. As far as software is concerned, licensed version of
Microsoft Access 2007 and Visual Basic 6.0 (Enterprise Version) should be
installed on the server. There should be printer attached to the network for printing
of various reports.

(2) Economic feasibility :


Economic feasibility looks at the financial aspects of the
project. Economic feasibility concerns with the returns from the investments in a
project. It determines whether it is worthwhile to invest the money in the proposed
system. It is not worthwhile spending a lot of money on a project for no returns.

To carry out an economic feasibility for a system, it is necessary to place actual


money value against any purchases or activities needed to implement the project.

The Advocate plans to acquire the necessary hardware and software require for the
system and there is no hindrance whether economical or otherwise towards its
purchase. A brief description of the hardware and software required in the system
is given later in the report

30
(3) Operational feasibility :
Operational feasibility covers two aspects. One is the technical
performance aspect and other is the acceptance within the system. Operational
feasibility determines how the proposed system will fit in the current operations
and what, if any job restructuring and retraining may be needed to implement the
system.

In the system operational feasibility checks, whether the user who is going to use
the system is able to work with the software’s with which the system is coded and
also the mind of the user going to use the system. If the user does not understand or
is able to work on the system further development is of waste.

31
Chapter 3

PROJECT PLAN

32
SYSTEM REQUIREMENTS SPECIFICATION

(1) HARDWARE REQUIREMENTS OF THE SYSTEM

This phase of the software development process deals with a brief study of
different hardware used in the computerized system. There is a list of hardware
materials used during the making and also during the use of the proposed system.
As the new system to be made into a computerized functional system, requirement
of a computer is must. All the hardware needed here are generally the basic
configuration of a typical Company computer. A list of the hardware requirement
used in the system given below:

o Minimum Configuration :
To run the application software of the system in the computer the minimum
configuration required is as below:

 233 MHz Pentium® processor or other compatible.

 Intel® Chipset Motherboard.

 32 MB SD-RAM.

 2 – 4 GB Hard-Disk.

 Monitor. [ 640 x 480 Display ]

 Keyboard.

 Mouse.

 Dot Matrix Printer.

33
o Recommended Configuration :
The system can run on the above mentioned system, however for perfect ness and
clearness it is recommended to use a computer system having the below listed
configuration. The configuration listed below can give best and optimum result at
instance during the working of the system.

 1 GHz Pentium® 4 processor or other compatible.

 Intel® 81x Chipset Motherboard.

 128 MB SD-RAM.

 10 GB Hard-Disk.

 Color Monitor. [ 1024 x 768 Display ]

 Keyboard.

 Mouse.

 132 Column Dot Matrix Printer/Laser Printers.

Note: The proposed system can work on both the above mentioned computer
configuration. It is just for knowledge that the system can also work with the old
technology as well as the new technology.

34
(2) SOFTWARE REQUIREMENTS OF THE SYSTEM

Along with the hardware, used in the system it requires software to make a
system as well as to run a system with the computer hardware. Collection of
different types of hardware into a specific type can form a computer but it cannot
execute different process on its own. For efficient and proper working of any
system software must be installed. These software may be in the form of operating
system or application software. To make the system one also needs to use software.

To make the Company Management System, I too have used certain software
which is listed below. The software used in the proposed system are the latest
versions of themselves and can give up-to-date and perfect result of every
processes in the system. This software comprises operating system and application
software used in the system.

Software used in designing (code) of the system:

 Operating System : Microsoft Windows® 2000/XP.

 Application Software’s : Microsoft Access 2007 [ back-end tool ]

Microsoft Visual Basic 6.0 [front-end tool]

35
TOOLS INFORMATION

 Microsoft Visual Basic 6.0 [Front-End]:


To develop any system along with the back-end tools which provide
access to the database and also solves the database queries like oracle, to make a
system interactive with the user the use of front-end tools comes into the picture.
The front-end tools make the user interface with the system easier and also provide
a user-friendly environment to the system.

This rich language enables you to develop many different types of


applications. You can create you can create programs that intersect with the
hardware.

It is a programming language used to create window base application.


Visual Basic is an old BASIC (Beginners All-purpose Symbolic instruction code)
language. It makes it very easy to get the user interface portion of your application
up and running.

Hundreds of functions and latest technological advances have been


added to the language to make it an industrial – strength development environment
suitable for almost my type of windows application. This is especially true with the
advent of internet programming and object oriented programming.

Microsoft Visual Basic 6.0 is one of the front-end tool provided by


Microsoft Inc. Microsoft Visual Basic 6.0 provides a fast way to develop
applications for Microsoft Windows. As a front-end tool Microsoft Visual Basic
6.0 provides the G.U.I interface to the user and it is supposed to be one of the beast
front-end tools used today.

36
Some of the main features of Visual Basic 6.0 are listed below:

 Data Access features allows you to create database and front-end applications
for most popular database formats, including Microsoft SQL Server, Oracle,
Microsoft Access and other enterprise level database.

 It includes a GUI environment fro making windows based applications.

 Active X technology allows you to use the functionality provided by other


application such as MS Word, MS Excel and other Windows applications. You
can even automate applications and professional or enterprise editions of Visual
Basic.

 Internet capabilities make it easy to provide access to documents and


applications across the internet from within your application.

 It provides a vital link to graphical environment and allows you to develop


applications based on standard Windows features : Dialog Boxes, Command
buttons, Pull down menus, Scroll bars, Selection lists etc. It also allows creating
robust applications that fully make use of the graphical user interface.

 A multitude of wizards and other graphical tools aid developers new to Visual
Basic.

 ADO-compliant data-bound controls.

 Hierarchical record sets and the Flex Grid Control.

 Visual Basic is an event driven programming language.

 Visual Basic allows you to adopt more of parallel approach, with independent
sections of code for each option that the user may select. This is known as
Event driven programming language.

37
 Visual data tools (VDTS).

 ADO Data Control (ADODC).

 Data report design and Data form wizards.

 It also helps the user with the SQL editor.

 By connecting it with Oracle, SQL statements can be run and terminated


through Visual Basic 6.0.

 Visual Basic Component creation.

 The language is very easy and it provides a very user friendly environment
while programming in Visual Basic 6.0.

 Packaging and Deployment wizard.

 Allows for the creation of p-code and native code EXE files. p-code is a
tokenized from of your source code that will be broken down at runtime into
machine code, which is why Visual Basic will create this intermediately forms.

 Can be extended easily through the use of windows API calls, hundreds of third
party controls and DLLs, and integration with other windows applications
through COM and DCOM.

 Has a shorter learning curve and development time than C/C++, Delphi, and
even Power Builder.

 Used by most of the Company suite tool as macro language. With the rest to
follow. Other companies as well are starting to support VBA in their products,
such as AutoCAD, Vision, CorelDraw, SAP, and many others.

 Allows for rapid application development and is excellent for business


applications.

38
 Has an excellent integrated help facility and book online as well as it includes
good debugging facilities and have many wizards that help automated repetitive
tasks.

 Object-based development is possible using class modules and rapid application


development (RAD).

 Allows for the creation of COM components such as Active X controls, DLL’s,
and Exec’s.

 Can integrate with the Internet on both the server side and the client side.

 Can create Active X Automation server.

 Integrates with Microsoft transaction server.

 Can run server either on the same machine or remotely on another computer.
This allow for true distributed processing.

39
ADVANTAGES OF VISUAL BASIC 6.0:

 During design time, it is possible to see how the program will look at the
runtime.

 Visual Basic is very useful in designing and developing, effective and


efficient windows based programs

 VB helps in making your program look quite effective and beautiful.

 You can add menus, tool bars, status bars, text boxes, etc. to blank window.

 It is less time consuming and more user friendly. Also user friendly
programs can be developed very easily.

DISADVANTAGES OF VISUAL BASIC 6.0:

 The programs that are developed utilize more memory.

 Visual Basic requires specific operating system which supports visual


programming.

 Graphical User Interface is provided by visual basic which takes some more
time then other non visual programming for execution of the program.

40
 MS ACCESS 2007

 INTRODUCTION TO MS ACCESS

Ms Access is a powerful multi-user DBMS developed by Microsoft


Corp. It can be used to store and manipulate large amounts of information
and automate repetitive tasks, such as maintaining an inventory and
generating invoices. By using Access, you can develop easy to use data input
forms. You can process your data and create meaningful reports.

 Features of ACCESS

Access is a multi-featured DBMS that can be used both by beginners


and those who have previous DBMS experience.

 Windows based application

Access is a windows-based application and therefore has an interface


similar to Windows 98/NT. You can cut copy and paste data from any
windows application to and from the Access.

 Large data management capacity

Access maintains a single disk file for a database and all its associated
objects. The Maximum size of this file can be 1 GB. Access allows a
maximum of 32,768 tables and objects in a database. However, Access can
create links to data tables in any other DBMS like FoxPro. Therefore, the

41
maximum size of tables and object objects is limited only by the amount of
storage space that the users have.

 Built-in Functions

Access includes mathematical, financial, date, time and string


functions. You can use them to create expressions for calculations in your
form, reports and queries.

 Built-in Security

Access is multi-user database, security features are built into the


DBMS. You can enable database security at various levels. You can assign a
password for loading Access so that only authorized users can use it. You can
encrypt a database to prevent unauthorized access.

 DATABASE:

Access stores all data tables and other objects in a single database. These
database objects are queries, forms, reports and macros.

42
DATA FLOW DIAGRAM(s) [D. F. D.]

Data flow diagram is a graphical tool used to describe and analyses


the movement of data through a system-manual or automated- including the
Processes stores the data, and delays in the system. Data flow diagrams are the
central tool and basis from which other components are developed.

The transformations of the data from input to output through the


Processes May be described logically and independently of the physical
components Associated with the system. They are termed logical data flow
diagrams. In contrast, physical data flow diagrams show the actual Implementation
and the movement of data between people departments and workstations.

The simple notations are easily understood by users and business


Persons who are part of the process being studied. Therefore analysts can work
With Users and actually involve them in the study of data flow diagrams.

Users can make suggestions for modifications of the diagrams to


More Accurately Described the business activity. They can also examine the charts
and spot Problems quickly so that they can be corrected before other design work
begins. If problems are not found early in the development process they will be
very difficult to correct when they are noticed. Avoiding mistakes early May even
prevent system failure.

Data flow analysis permits analysts to isolate areas of interest in the


Company and study them by examining the data that enter the process and seeing

43
how they are changed when they are changed when they leave the process. As
analyst gather acts and details their increased understanding of the process leads
them to ask questions about specifications of the process which leads to still
additional investigation as the area of investigation is broken into successively
lower level details until all the essential components and their interrelations can be
understood.

A comprehensive system investigation produces sets of many data


flow diagrams some providing overviews of major processes and others going into
great details to show data elements, data stores, and processing steps for specific
components of a larger system. If analysts want to review the overall system later,
they use the higher-level overview diagrams. However if they are interested in
studying one particular they use the data flow diagram for that lower process.

The levels of data flow diagrams can be compared to highway and


street Maps that you might use when traveling in an unfamiliar area. You first use
a national map, showing major highways and cities. As you near the city you are
visiting you need a more detailed map showing the major parts of the city and the
access roads. After you reach the area of the city you want, a detailed street map
that shows even important landmarks, such as bridges and buildings, is especially
helpful. This much detail is essential when you are first starting on the trip and
attempting to understand the lay of the land.

The data flow diagrams are pictorial or graphical representation of the

outline of the system study. The data flow diagram covers all the processes and

data storage area, which takes place during any transaction in the system. The data

44
flow diagrams are functionally divided into context level, Zero level and first level

data flow diagrams.

Symbols used in DFDs:

(1) Process: Here flow of data is transformed. E.g. Calculations, etc.

(2) External Entity: A source or destination of data which is external to


the system. E.g. Patient etc.

(3) A data flow: It is packet of data. It may be in the form of document,


letter etc.

(4) Data store: Any store data but with no reference to the physical
method of storing.

45
CONTEXT LEVEL DIAGRAM

46
DATA FLOW DIAGRAMS

1. MASTER MAINTAINENCE

47
2. CUSTOMER SALES ORDER & DEPOSIT AND
INVOICE GENERATION

48
3. SUPPLIER PURCHASE ORDER & PAYMENT

49
4. TEST REPORT :

50
5. REPORT GENERATION :

51
ENTITY – RELATIONSHIP DIAGRAM

52
GANTT CHART :

When creating a project schedule we start with a set task . effort , duration and start
date are important to be noted to keep track of the progress of the system
development at various stages we divide the all tasks between the two of us as a
consequences of this input a timeline chart also called a Gantt chart is generated

The chart reflects the entire project lifecycle instead of each project function or
each individualworking on the project and gives an overview of the timeline of
project development lifecycle.

53
TASK NAME DURATION TIME TAKEN

PLANNING NOV 05to NOV 30 24 DAYS

----Understanding Problem Definition 18Days

----Project Feasibility 6 Days

----Planning Complete

ANALYSIS PHASE DEC 1 to DEC 30 30 DAYS

----Gathering Information 8 Days

----Defining System Requirements 15 Days

----Generate Alternatives 5 Days

----Review Recommendations 2 Days

----Analysis Complete

DESIGN PHASE JAN 1 to FEB 25 56DAYS

----Design User Interface 22 Days

----Design And Integrate Database 28Days

----Design And Integrate System Control 6 Days

----Design Complete

IMPLEMENTATION PHASE FEB 21 to MAR 15 24 DAYS

----Construct Software Components 8 Days

----Verify And Testing 10 Days

----Documentation 6 Days

----Implementation Still Pending

54
55
Chapter 5

DATA
DICTIONARY

56
DATA DICTIONARY

The data dictionary of any system is an integral component of structure analysis,


since data flow diagrams by themselves do not fully describe the subject under
investigation about the system.

A data dictionary is a catalog – a repository – of the elements in


the system. These elements center on data and the way they are structured to meet
user requirements and Metal Firm Management System needs. This step of
creating a data dictionary is simultaneous with the process of making data flow
diagram(s). Here all the data fields in their respective tables are allotted so as to
access these data in the system. The data tables are created in a back-end tool like
Microsoft Access, Oracle, FoxPro, etc…. Here in the proposed system we are
using tables created in Microsoft Access 2007 as it is the back-end tool used in the
system.

The data dictionary consists of different major elements like Data


Elements, Data Store [Tables Used], Data Flow, Processes and other External
entities used in the system. The data dictionary stores details and description of
these elements.

It is developed during data flow analysis and assists the analysts involved
in determining the system requirements. Analysts use data dictionary for the
following important reasons:

 To manage the details in large system.

 To communicate a common meaning for all system elements.

 To document the features of the system.

 System changes should be made.


57
Data dictionary in detail

 Manage details

Large systems have high volumes of data flowing through them in the form
documents, reports, and even conversations. Similarly many different activities
take place that use existing data or create new details.

It is impossible for system analyst to remember it all. Those who try invariably
make mistakes or forget important elements. The best analysts don’t even try they
record the information. Some write the descriptions on the paper and others use
index cards.

Many enter the details into word processor, running, perhaps, on a personal
computer. The best-organized and most effective analysts use automated data
dictionaries designed specifically for systems analysis and design.

 Communicate meaning

Data dictionaries assist in ensuring common meanings for


system elements and activities. If you examine the sample data flow diagrams for
order processing, you probably will have little trouble understanding what such
data as invoice and bank check represent.

Data dictionaries record additional details about the data flow in system so that all
persons involved can quickly look up the description of data flows, data stores, or
processes.

58
 Document system features

We want to know about the processes and data stores of course. Having to formally
describe system features will produce a more complete understanding.

 Facilitate Analysis

The fourth reason for using data dictionaries is to determine whether new features
are needed in a new system or whether changes of any type are in order.

(1) Nature of Transactions

The business activities that will be carried on while using the system including the
data needed to accept authenticate and process each activity.

(2) Inquiries

Request for the retrieval of information or processing to be for generate specific


response.

(3) Output and Report Generation

Results of system processing presented to users and admin in an acceptable form

(4) Files and Data Bases

The details of all the transactions contained in database and files required to run
our software authentically.

Example: What data must be captured to verify the accuracy and authenticity of
transactions?

(5) System Capacity

The capacity of the system to accept, processes, and stores Transactions and data.

59
(6) Locate Errors And Omissions:

Having information in a dictionary about these system characteristics-


transactions, inquires, data and capacity-will tell you great deal about a system and
allow you to evaluate it. But you need to know that the information itself is
complete and accurate. Therefore dictionaries are used for a fifth reason:

To locate errors in the system description we have Conflicting data flow


descriptions, processes that neither receive input nor generate output, data stores
that are never updated etc., indicate incomplete or incorrect analysis that we want
to correct before determining systems that changes are needed. Automated data
dictionary systems have features that will detect these difficulties for you and
present them in report. But even in manual dictionaries, the process of recording
the information will usually reveal errors.

60
DATA STORE

The following tables are used in the Eye Metal Firm Management System:

1. SUPPLIER

Field Name Data Size Constraint


Supplier_no Number 4 Primary Key
Company_name Text
Type 50 Not Null
Company_code Text 4 Not Null
Owner Text 50 Not Null
Panno Text 10 Not Null
Address Text 100 Not Null
Salesman_name Text 50 Not Null
Telno Text 11 Not Null
Fax Text 11 Not Null
Email Text 50 Not Null
desciption Text 100 Not Null

2. CUSTOMER

Field Name Data Size Constraint


customer_no Number 4 Primary Key
Company_name Text
Type 50 Not Null
Company_code Text 4 Not Null
Owner Text 50 Not Null
Panno Text 10 Not Null
Address Text 100 Not Null
Telno Text 11 Not Null
Fax Text 11 Not Null
Email Text 50 Not Null
desciption Text 100 Not Null

61
3. EMPLOYEE

Field Name Data Size Constraint


Employee_no Number 4 Primary Key
Fname Text
Type 50 Not Null
Lname Text 50 Not Null
Mname Text 50 Not Null
Doj Date/Time 10 Not Null
Gender Text 1 Not Null
Address Text 100 Not Null
telno Text 11 Not Null
Altno Text 11 Not Null
Mobile Text 10 Not Null
Dept Text 50 Not Null
Qualification Text 100 Not Null
Workex Text 100 Not Null
Panno Text 10 Not Null
Dob Date/Time 10 Not Null
Basic Number 6 Not Null
Pf Number 6 Not Null
Hra Number 6 Not Null
Tax Number 6 Not Null
Uname Text 50 Not Null
Password Text 50 Not Null
Da Number 6 Not Null
Ta Number 6 Not Null

62
4. PAYMENT

Field Name Data Size Constraint


payment_no Number 4 Primary Key
Pdate Date/Time
Type 11 Not Null
Customer no Text 50 Not Null
Type Text 8 Not Null
Bank Text 50 Not Null
Branch Text 50 Not Null
Cheque Text 6 Not Null
Description Number 50 Not Null
Total Number 6 Not null

5. PRODUCT

Field Name Data Size Constraint


Product id Number 4 Primary Key
Product name Text
Type 4 Not null
Product type Number 4 Not Null
Overall qty Text 12 Not Null
Qty in hand Date/Time 10 Not Null
Cost/per peice Number 8 Not Null
Sell price Number 8 Not Null

63
6. PURCHASE

Field Name Data Size Constraint


purchase_no Number 4 Primary Key
Pdate Date/Time
Type 10 Not Null
Order no Number 4 Not Null
Supplier_no Number 8 Not Null
Company name Text 4 Not Null
Product type Number 8 Not Null
Product id Number 6 Not Null
No of pieces Number 12 Not Null
Ppc Number 6 Not Null
Total Number 6 Not Null

7. ORDER

Field Name Data Size Constraint


order_no Number 4 Primary Key
odate Date/Time
Type 10 Not Null
customer_no Number 4 Not Null
Product id Text 8 Not Null
Product type Text 4 Not Null
Product name Text 8 Not Null
qty Number 6 Not Null
ppp Number 12 Not Null
total Number 6 Not Null

64
8. Testing

Field Name Data Type Size Constraint


Ref no Auto 4 Primary Key
Customer name Text 10 Not Null
Testing material Text
Number 4 Not Null
Test site Text 8 Not Null
Surface condition Text 4 Not Null
Basic cali blocks Number 8 Not Null
prrobe Number 6 Not Null
frequency Text 12 Not Null
size Number 6 Not Null
type Text 6 Not Null
Scanning Text 4 Not Null
Couplant Text 50 Not Null

9. Bill

Field Name Data Size Constraint


Bill no Number 4 Primary Key
Ref no Date/Time
Type 10 Not Null
Bill date Number 4 Not Null
Customer name Text 8 Not Null
qty Date/Time 4 Not Null
particulars Number 8 Not Null
rate Number 6 Not Null
perpeice Text 12 Not Null
total Number 6 Not Null

65
Chapter 6

ARCHITECTURAL
Design

66
SCREENS [INTERFACES OF THE SYSTEM]

FORM LAYOUTS

This section refers to the various types of interfaces which the user has to face
during operating the computerized system of “Metal Firm Management System”.

The section refers with the entire interface [Screens] a user will have to face
while operating the current system. It shows the various screens appearing for
different transactions. All the screens of different transactions in the system are
shown here.

The different transaction’s screens shown here.

67
Form No 1
Form Name MDIMain
Purpose This is the main form of the system which contains all the
different forms and menus.
Type MDI

68
Form No 2
Form Name Frm_employee
Purpose This form is used to add, modify,delete and view
employees.
Type MDIChild

69
Form No 3
Form Name Frm_customer
Purpose This form is used to add, modify,delete and view broker.
Type MDIChild

70
Form No 4
Form Name Frm_supplier
Purpose This form is used to add, modify,delete and view
supplier.
Type MDIChild

71
Form No 5
Form Name Frm_testing
Purpose This form is used to add, modify,delete and view test
report
Type MDIChild

72
Form No 5
Form Name Frm_product
Purpose This form is used to add, modify,delete and view
different product .
Type MDIChild

73
Form No 6
Form Name Frm_purchase
Purpose This form is used to add, modify,delete and view
purchase details.
Type MDIChild

74
Form No 7
Form Name Frm_billgenaration
Purpose This form helps the user to create bill for test report
Type MDIChild

75
Form No 8
Form Name Frm_payment
Purpose This form helps the user to register the payments made
except the supplier payment.
Type MDIChild

76
Form No 9
Form Name Frm_changepswd
Purpose This form helps the user to change his/ password.
Type MDIChild

77
Form No 10
Form Name Frm_splash
Purpose This form is displayed to the user when the user clicks on
the Exe file to start the system.
Type MDIChild

78
Form No 11
Form Name Frm_login
Purpose This form is used for security of the system. Only
authorized users can log in using their password. This for
is displayed at the start the system.
Type MDIChild

79
REPORT GENERATION
1. Employee Pay Slip Generation

Report No 1
Form Name DataReport1
Purpose This Report generates the salary break-up of the
employee whose name is entered.
Type MDIChild

80
2. Customer Deposits Pending

Report No 2
Form Name DataReport3
Purpose This Report generates the details of Customers which
have to make payments for their orders.
Type MDIChild

81
3. Supplier Payment Pending

Report No 4
Form Name DataReport4
Purpose This Report generates the details of Suppliers and the
product details of which the company has to make the
payment.
Type MDIChild

82
FUTURE ENHANCEMENT

 Employee Holiday Management.

.
 Will Include Reminders for the employees.

 Will include a Log file.

 Will make the software distributed.

 Will include a daily attendance record.

83
CODING
 frm_employee
Dim CON As New ADODB.Connection
Dim RS As New ADODB.Recordset

Private Sub cmd_cancel_Click()


Unload Me
End Sub

Private Sub cmd_clear_Click()


ADO.Recordset.AddNew
End Sub

Private Sub cmd_delete_Click()


ans = MsgBox("Are you sure you want to delete this record ? ", vbYesNo + vbQuestion,
"DELETE BROKER DETAILS")
If ans = vbYes Then
ADO.Recordset.Delete
Call cmd_next_Click
Else
Exit Sub
End If
End Sub

Private Sub cmd_next_Click()


On Error Resume Next
ADO.Recordset.MoveNext
If ADO.Recordset.EOF Then
MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD REACHED"
ADO.Recordset.MoveLast
End If
End Sub

Private Sub cmd_prev_Click()


On Error Resume Next
ADO.Recordset.MovePrevious
If ADO.Recordset.BOF Then
MsgBox "This is the first record.", vbInformation + vbOKOnly, "FIRST RECORD REACHED"
ADO.Recordset.MoveFirst
End If
End Sub

84
Private Sub cmd_save_Click()
If txtempid = "" Then
MsgBox "Please enter the Employee Number.", vbOKOnly + vbCritical, "Warning - Invalid
Customer Number."
txtempid.SetFocus
Exit Sub
End If

If txtfname = "" Then


MsgBox "Please enter the Employee's First Number.", vbOKOnly + vbCritical, "Warning -
Invalid Customer Name."
txtfname.SetFocus
Exit Sub
End If

If txtlname = "" Then


MsgBox "Please enter the Employee's Last Number.", vbOKOnly + vbCritical, "Warning -
Invalid Customer Name."
txtlname.SetFocus
Exit Sub
End If

If txttelno = "" And txtmobile = "" And txtaltno = "" Then


MsgBox "Please enter the Employee's Contact details.", vbOKOnly + vbCritical, "Warning -
Invalid Customer Contact Details."
txttelno.SetFocus
Exit Sub
End If

If txtbasic = "" Or txthra = "" Or txttax = "" Or txtpf = "" Then


MsgBox "Please enter the Employee's Salary Break up", vbOKOnly + vbCritical, "Warning -
Invalid Employee Salary Details"
txtbasic.SetFocus
Exit Sub
End If

If txtpanno = "" Then


MsgBox "Please enter the Employee's PAN Number.", vbOKOnly + vbCritical, "Warning -
Invalid Customer Name."
txtlname.SetFocus
Exit Sub
End If

If txtcpwd = "" Or txtpwd = "" Or txtcpwd <> txtpwd Then


MsgBox "Please enter the password and the Confirm password", vbCritical + vbOKOnly,
"Warning - Invalid Password."

85
Exit Sub
End If

ADO.Recordset.Fields(0) = Val(txtempid)
ADO.Recordset.Fields(1) = txtfname
ADO.Recordset.Fields(2) = txtlname
ADO.Recordset.Fields(3) = txtmname
'ADO.Recordset.Fields(4) = txtdoj
If optM.Value = True Then
ADO.Recordset.Fields(5) = "M"
Else
ADO.Recordset.Fields(5) = "F"
End If
ADO.Recordset.Fields(6) = txtaddress
ADO.Recordset.Fields(7) = txttelno
ADO.Recordset.Fields(8) = txtaltno
ADO.Recordset.Fields(9) = txtmobile
ADO.Recordset.Fields(10) = txtdept
ADO.Recordset.Fields(11) = txtqualification
ADO.Recordset.Fields(12) = txtwe
ADO.Recordset.Fields(13) = txtpanno
'ADO.Recordset.Fields(14) = txtdob
ADO.Recordset.Fields(15) = txtbasic
ADO.Recordset.Fields(16) = txtpf
ADO.Recordset.Fields(17) = txthra
ADO.Recordset.Fields(18) = txttax
ADO.Recordset.Fields(19) = txtfname & txtlname
ADO.Recordset.Fields(20) = txtpwd
ADO.Recordset.Fields(21) = txtda
ADO.Recordset.Fields(22) = txtta
ADO.Recordset.Save

MsgBox "The Record has been added to the database.", vbInformation + vbOKOnly, "ENTRY
SAVED"

End Sub

Private Sub Form_Load()


CON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path &
"\pinkstars.mdb;Persist Security Info=False"
End Sub

Private Sub Form_Unload(Cancel As Integer)


CON.Close
End Sub

86
 Frm_customer

Dim ADOCON As New ADODB.Connection

Dim RS As New ADODB.Recordset

Private Sub cmdadd_Click()


' Adodc1.Recordset.AddNew

MsgBox "A new record has been added to the CUSTOMER table"

End Sub

Private Sub cmddelete_Click()


ans = MsgBox(" Are you sure you want to delete this RECORD ? ", vbYesNo +
vbQuestion, "DELETE SUPPLIER PAYMENT ")
If ans = vbYes Then
ADO.Recordset.Delete
RS.Open "update purchase set payment_no = 0 where purchase_no like " &
Val(cbopurchaseno.Text), CON, adOpenDynamic, adLockOptimistic
MsgBox "The Record has been deleted.", vbInformation + vbOKOnly, "Supplers Details
Deleted"
Call cmd_next_Click

End If

End Sub

Private Sub cmdexit_Click()


End
End Sub

Private Sub cmdnext_Click()


On Error Resume Next
Adodc1.Recordset.MoveNext

If Adodc1.Recordset.EOF Then
MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD
REACHED"
Adodc1.Recordset.MoveLast

87
End If

End Sub

Private Sub cmdprevious_Click()

On Error Resume Next


Adodc1.Recordset.MovePrevious

If Adodc1.Recordset.BOF Then
MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST RECORD
REACHED"
Adodc1.Recordset.MoveFirst
End If
End If

End Sub

Private Sub cmdshow_Click()


custid = Val(txtcustno)
strsql = " select * from sup_customer where custid = " & custid & " "
Set RS = ADOCON.Execute(strsql)

txtcustno.SetFocus
txtcname = RS.Fields(1)
txtccode = RS.Fields(2)
txtowner = RS.Fields(3)
txtcadd = RS.Fields(4)
txtpanno = RS.Fields(5)
txttelno = RS.Fields(6)
txtemail = RS.Fields(7)
'txtdesc = RS.Fields(8)
Private Sub Form_Load()

ADOCON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\ty\testing.mdb;Persist Security Info=False"
RS.Open "select * from sup_customer ", ADOCON, adOpenDynamic, adLockOptimistic

End Sub

88
 Frm_testing
Dim ADOCON As New ADODB.Connection
Dim RS1 As New ADODB.Recordset
Dim RS As New ADODB.Recordset

Private Sub cmd_add_Click()

Adodc1.Recordset.AddNew
' Adodc1.Recordset.Update

MsgBox "A new record has been added to the TESTING table"

ans = MsgBox(" DO YOU WANT TO CONTINUE TO BILL PAGE ? ", vbYesNo +


vbQuestion, "SHOW BILL PAGE ")
If ans = vbYes Then
frmbillgen.Show
End If

End Sub

Private Sub cmd_exit_Click()


End
End Sub

Private Sub cmd_next_Click()


On Error Resume Next
Adodc1.Recordset.MoveNext

If Adodc1.Recordset.EOF Then
MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD
REACHED"
Adodc1.Recordset.MoveLast
End If

End Sub

Private Sub cmd_prev_Click()


On Error Resume Next
Adodc1.Recordset.MovePrevious

If Adodc1.Recordset.BOF Then

89
MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST RECORD
REACHED"
End If

End Sub

Private Sub cmd_show_Click()


refno = Val(txtrefno)
strsql = " select * from testing"
Set Adodc1.Recordset = ADOCON.Execute(strsql)

For i = 0 To Adodc1.MaxRecords

If Adodc1.Recordset.Fields(1) = refno Then

txtcust = Adodc1.Recordset.Fields(1)
txtxmaterial = Adodc1.Recordset.Fields(2)
txtsite = Adodc1.Recordset.Fields(3)
cbosurface = Adodc1.Recordset.Fields(4)
cbobasic_cb = Adodc1.Recordset.Fields(5)
txtprobe = Adodc1.Recordset.Fields(6)
txtfrequency = RS.Fields(7)
txtsize = Adodc1.Recordset.Fields(8)
txttype = Adodc1.Recordset.Fields(9)
cbo_scanning = Adodc1.Recordset.Fields(10)
cbo_couplant = Adodc1.Recordset.Fields(11)

End If
Adodc1.Recordset.MoveNext

Next i

'setting visibility to false

'txtcust.Enabled = False
'txtxmaterial.Enabled = False
'txtsite.Enabled = False
'cbosurface.Enabled = False
'cbobasic_cb.Enabled = False
'txtprobe.Enabled = False
'txtfrequency.Enabled = False
'txtsize.Enabled = False
'txttype.Enabled = False
'cbo_scanning.Enabled = False
'cbo_couplant.Enabled = False

90
End Sub

Private Sub Form_Load()


ADOCON.Open "Provider = Microsoft.Jet.OLEDB.4.0;Data
Source=C:\ty\testing.mdb;Persist Security Info=False"
RS.Open "select * from testing", ADOCON

'options for cbosuface


cbosurface.AddItem " AS ROLLED "
cbosurface.AddItem " FORGED "
cbosurface.AddItem " Machined"
cbosurface.AddItem " Normalised "

'options for cbo_couplant


cbo_couplant.AddItem " Water"
cbo_couplant.AddItem "Oil "
cbo_couplant.AddItem "Grease"

'options for cbo_scanning


cbo_scanning.AddItem " Normal Beam "
cbo_scanning.AddItem " Angle Beam of Complete Surface"

'options for cbobasic_cb


cbobasic_cb.AddItem "IIW"
cbobasic_cb.AddItem "VI"
cbobasic_cb.AddItem "V2"
cbobasic_cb.AddItem "SDH"
cbobasic_cb.AddItem "FBH"

Adodc1.Recordset.MoveFirst

End Sub

91
 Frm_supplier

Dim ADOCON As New ADODB.Connection

Dim RS As New ADODB.Recordset

Private Sub cmdadd_Click()


ADO.Recordset.AddNew

MsgBox "A new record has been added to the BILLGEN table"

End Sub

Private Sub cmddelete_Click()


ans = MsgBox(" Are you sure you want to delete this RECORD ? ", vbYesNo +
vbQuestion, "DELETE SUPPLIER PAYMENT ")
If ans = vbYes Then
ADO.Recordset.Delete
RS.Open "update purchase set payment_no = 0 where purchase_no like " &
Val(cbopurchaseno.Text), CON, adOpenDynamic, adLockOptimistic
MsgBox "The Record has been deleted.", vbInformation + vbOKOnly,
"Supplers Details Deleted"
Call cmd_next_Click

End If

End Sub

Private Sub cmdexit_Click()


End
End Sub

Private Sub cmdnext_Click()


On Error Resume Next
ADO.Recordset.MoveNext

If ADO.Recordset.EOF Then
MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST
RECORD REACHED"
ADO.Recordset.MoveLast

End If

92
End Sub

Private Sub cmdprevious_Click()

On Error Resume Next


ADO.Recordset.MovePrevious

If ADO.Recordset.BOF Then
MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST
RECORD REACHED"

End If

End Sub

Private Sub cmdshow_Click()

supplierid = Val(txtsuppno)
strsql = " select * from supplier where supplierid = " & supplierid & " "
Set RS = ADOCON.Execute(strsql)

txtsuppno.SetFocus
txtcname = RS.Fields(0)
txtccode = RS.Fields(1)
txtowner = RS.Fields(2)
txtcname = RS.Fields(3)
txtsuppname = RS.Fields(4)
txtpanno = RS.Fields(5)
txtcadd = RS.Fields(6)
txttelno = RS.Fields(7)
txtemail = RS.Fields(8)

End Sub

Private Sub Form_Load()

ADOCON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\ty\testing.mdb;Persist Security Info=False"
RS.Open "select * from supplier ", ADOCON, adOpenDynamic,
adLockOptimistic

'ADO.Recordset.MoveFirst

End Sub

93
 Frm_order
Dim ADOCON As New ADODB.Connection

Dim RS As New ADODB.Recordset

Private Sub cmdadd_Click()

ADO.Recordset.AddNew

MsgBox "A new record has been added to the BILLGEN table"

End Sub

Private Sub cmddelete_Click()

ans = MsgBox(" Are you sure you want to delete this RECORD ? ", vbYesNo + vbQuestion, "DELETE
ORDER DETAILS ")

If ans = vbYes Then

ADO.Recordset.Delete

RS.Open "update purchase set payment_no = 0 where purchase_no like " & Val(cbopurchaseno.Text),
CON, adOpenDynamic, adLockOptimistic

MsgBox "The Record has been deleted.", vbInformation + vbOKOnly, "Supplers Details Deleted"

Call cmd_next_Click

End If

End Sub

94
Private Sub cmdexit_Click()

End

End Sub

Private Sub cmdnext_Click()

On Error Resume Next

ADO.Recordset.MoveNext

If ADO.Recordset.EOF Then

MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD REACHED"

ADO.Recordset.MoveLast

End If

End Sub

Private Sub cmdprevious_Click()

On Error Resume Next

ADO.Recordset.MovePrevious

If ADO.Recordset.BOF Then

MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST RECORD REACHED"

ADO.Recordset.MoveFirst

End If

95
End Sub

Private Sub cmdshow_Click()

orderno = Val(txtorderno)

strsql = " select * from sup_order where orderno = " & orderno & " "

Set RS = ADOCON.Execute(strsql)

txtorderno.SetFocus

txtdate = RS.Fields(1)

txtsupplierid = RS.Fields(2)

txtproductid = RS.Fields(3)

txtproducttype = RS.Fields(4)

txtname = RS.Fields(5)

txtquantity = RS.Fields(6)

End Sub

Private Sub Command1_Click()

txtamount = Val(txtquantity) * Val(txtpricepp)

Call cmdadd_Click

End Sub

Private Sub Form_Load()

ADOCON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\ty\testing.mdb;Persist Security


Info=False"

RS.Open "select * from sup_order ", ADOCON, adOpenDynamic, adLockOptimistic

'ADO.Recordset.MoveFirst

End Sub

96
 Frm_purchase

Dim ADOCON As New ADODB.Connection

Dim RS As New ADODB.Recordset

Private Sub cmdadd_Click()

'If txtproductid = 1 Then

' txtptype = RS.Fields(8)

' txtproductname = RS.Fields(6)

'End If

ADO.Recordset.AddNew

MsgBox "A new record has been added to the PURCHASE table"

End Sub

Private Sub cmddelete_Click()

' NT TESTED

'ans = MsgBox(" Are you sure you want to delete this RECORD ? ", vbYesNo + vbQuestion,
"DELETE PURCHASE DETAILS ")

'If ans = vbYes Then

'ADO.Recordset.Delete

97
'RS.Open "update purchase set payment_no = 0 where purchase_no like " &
Val(cbopurchaseno.Text), CON, adOpenDynamic, adLockOptimistic

'MsgBox "The Record has been deleted.", vbInformation + vbOKOnly, "Supplers Details
Deleted"

'Call cmd_next_Click

'End If

End Sub

Private Sub cmd_cancel_Click()

End

End Sub

Private Sub cmd_next_Click()

On Error Resume Next

ADO.Recordset.MoveNext

If ADO.Recordset.EOF Then

MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD REACHED"

ADO.Recordset.MoveLast

End If

End Sub

98
Private Sub cmd_prev_Click()

On Error Resume Next

ADO.Recordset.MovePrevious

If ADO.Recordset.BOF Then

MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST RECORD
REACHED"

ADO.Recordset.MoveFirst

End If

End Sub

Private Sub cmdview_Click()

purchaseno = Val(txtpurchaseno)

strsql = " select * from sup_purchase where purchaseno = " & purchaseno & " "

Set RS = ADOCON.Execute(strsql)

txtpurchaseno.SetFocus

txtpdate = RS.Fields(1)

txtorderno = RS.Fields(2)

txtsupno = RS.Fields(3)

txtcname = RS.Fields(4)

99
txtproductid = RS.Fields(5)

txtproductname = RS.Fields(6)

txtpeices = RS.Fields(7)

txtptype = RS.Fields(8)

txtppc = RS.Fields(9)

txttotal = RS.Fields(10)

End Sub

private Sub Form_Load()

ADOCON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\ty\testing.mdb;Persist


Security Info=False"

RS.Open "select * from sup_purchase ", ADOCON, adOpenDynamic, adLockOptimistic

End Sub

100
 Frm_payment

Dim ADOCON As New ADODB.Connection

Dim RS As New ADODB.Recordset

Private Sub cmd_cancel_Click()

End

End Sub

Private Sub cmd_clear_Click()

'CLEAR

ADO.Refresh

ADO.Recordset.AddNew

cmd_save.Enabled = True

End Sub

Private Sub cmd_next_Click()

'CLEAR

On Error Resume Next

ADO.Recordset.MoveNext

If ADO.Recordset.EOF Then

MsgBox "This is the last record.", vbInformation + vbOKOnly, "LAST RECORD REACHED"

ADO.Recordset.MoveLast

End If

Call cmdview_Click

101
End Sub

Private Sub cmd_print_Click()

'CLEAR

cdlgprint.ShowPrinter

End Sub

Private Sub cmd_prev_Click()

On Error Resume Next

ADO.Recordset.MovePrevious

If ADO.Recordset.BOF Then

MsgBox " This Is The First record", vbInformation + vbOKOnly, "FIRST RECORD
REACHED"

ADO.Recordset.MoveFirst

End If

End Sub

Private Sub cmd_save_Click()

'CLEAR

If txtpaymentno = "" Then

MsgBox "Please enter the Payment Number.", vbOkOk + vbCritical, "Warning - Invalid
Payment Number."

txtpaymentno.SetFocus

102
Exit Sub

End If

If txtpaymentdate = "" Then

MsgBox "Please enter the date when payment was made.", vbOkOk + vbCritical, "Warning -
Invalid Payment date."

txtpaymentdate.SetFocus

Exit Sub

End If

If txttotal = "" Then

MsgBox "Please enter the Payment Amount Detail.", vbOkOk + vbCritical, "Warning - Invalid
Payment Details. "

txttotal.SetFocus

Exit Sub

End If

If RS.Supports(adAddNew) Then

With RS

.AddNew

.Fields("paymentno") = txtpaymentno

.Fields("billno") = txtbillno

.Fields("refno") = txtrefno

.Fields("customer name") = txtpaymentfrom

.Fields("paymentdate") = txtpaymentdate

.Fields("paymenttype") = txtpaymentfrom

.Fields("bankname") = txtbname

103
.Fields("branch") = txtbranch

.Fields("cheque") = txtchqno

.Fields("totalamount") = txttotal

.Update

End With

MsgBox "A new record has been added to the PAYMENT table"

End If

End Sub

Private Sub cmdview_Click()

paymentno = Val(txtpaymentno)

strsql = " select * from payment where paymentno = " & paymentno & " "

Set RS = ADOCON.Execute(strsql)

txtbillno = RS.Fields(1)

txtrefno = RS.Fields(2)

txtpaymentfrom = RS.Fields(3)

'txtpaymentdate = RS.Fields(4)

txtpaymenttype = RS.Fields(5)

txtbname = RS.Fields(6)

txtbranch = RS.Fields(7)

txtchqno = RS.Fields(8)

txttotal = RS.Fields(9)

' txtdesc = RS.Fields(10)

104
End Sub

Private Sub Form_Load()

'CLEAR

ADOCON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\ty\testing.mdb;Persist


Security Info=False"

RS.Open " select * from payment ", ADOCON

ADO.Recordset.MoveFirst

'txtbillno = Val(frmbillgen.txtbillno)

'txtpaymentfrom = frmbillgen.txtcname

'txttotal = Val(frmbillgen.txttotal)

'txtbillno.Enabled = False

'txtpaymentfrom.Enabled = False

'txttotal.Enabled = False

End Sub

Private Sub optCash_Click()

' CLEAR

txtbname = ""

txtbranch = ""

txtchqno = ""

Frame3.Enabled = False

txttop = "CASH"

End Sub

105
Private Sub optCheque_Click()

'CLEAR

Frame3.Enabled = True

txttop = "CHEQUE"

End Sub

106
 Frm_stocksummaryselection
Public A As String

Private Sub cmd_cancel_Click()


Me.Hide
End Sub

Private Sub cmd_summary_Click()


frm_stocksummaryselection.Hide
frm_stocksummary.Show
End Sub

Private Sub cmd_view_Click()


A = Mid(cbotod.Text, 1, 2)
Me.Hide
frm_stockdetail.Show
frm_stockdetail.ADO.RecordSource = "select product.purchase_no,
product.lot_no,product.pdate,product.carats,
product.diamondtype,product.peices,product.ppc,purchase.oname,purchase.cname,product.crem,
product.prem from product, purchase where purchase.purchase_no=product.purchase_no And
product.diamondtype like " & "'" & A & "%" & "'"
frm_stockdetail.ADO.Refresh
If frm_stockdetail.ADO.Recordset.EOF = True Then
MsgBox "There are diamonds in the " & cbotod.Text & " Collection" & vbCrLf & "Please select
another option from the list. ", vbOKOnly + vbInformation, "Warning - Invalid Diamond Type"
frm_stockdetail.Hide
frm_stocksummaryselection.Show
Exit Sub
End If
End Sub

107
 Frm_changepwd
Dim CON As New ADODB.Connection
Dim RS As New ADODB.Recordset

Private Sub cmd_cancel_Click()


Unload Me
End Sub

Private Sub cmd_save_Click()


If txtpass = "" Or txtcpass = "" Then
MsgBox "Please fill in your password. ", vbCritical + vbOKOnly, "Warning - Invalid
password"
End If

If txtpass <> txtcpass Then


MsgBox "The New password and the Confirmation password do not match.",
vbCritical + vbOKOnly, "Warning - Invalid Password"
Exit Sub
End If
A = MsgBox("Are u sure u want to change your Password ? ", vbYesNo +
vbInformation, "PASSWORD CHANGE CONFIRMATION ")
If A = vbYes Then
RS.Open "select * from employee where uname = " & "'" & cbouname.Text & "' And
password = " & "'" & txtoldpwd & "'", CON, adOpenDynamic, adLockOptimistic
If RS.EOF Then
MsgBox "The Old password does not match with the database. Retry.", vbCritical +
vbOKOnly, "Warning - Invalid Password."
Exit Sub
End If

RS.Fields(20).Value = txtpass.Text
RS.Update
RS.Close
MsgBox "Your Password has been updated.", vbInformation + vbOKOnly,
"Password Change Confirmation"
End If
End Sub

Private Sub Form_Load()


ADO.Refresh
ADO.Recordset.MoveFirst
While ADO.Recordset.EOF <> True
cbouname.AddItem (ADO.Recordset.Fields(0))
ADO.Recordset.MoveNext
Wend

108
CON.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path &
"\pinkstars.mdb;Persist Security Info=False"
End Sub

Private Sub Form_Unload(Cancel As Integer)

109
 Frm_calculator
Option Explicit
Dim Op1, Op2 ' Previously input operand.
Dim DecimalFlag As Integer ' Decimal point present yet?
Dim NumOps As Integer ' Number of operands.
Dim LastInput ' Indicate type of last keypress event.
Dim OpFlag ' Indicate pending operation.
Dim TempReadout

' Click event procedure for C (cancel) key.


' Reset the display and initializes variables.
Private Sub Cancel_Click()
Readout = Format(0, "0.")
Op1 = 0
Op2 = 0
Form_Load
End Sub

' Click event procedure for CE (cancel entry) key.


Private Sub CancelEntry_Click()
Readout = Format(0, "0.")
DecimalFlag = False
LastInput = "CE"
End Sub

' Click event procedure for decimal point (.) key.


' If last keypress was an operator, initialize
' readout to "0." Otherwise, append a decimal
' point to the display.
Private Sub Decimal_Click()
If LastInput = "NEG" Then
Readout = Format(0, "-0.")
ElseIf LastInput <> "NUMS" Then
Readout = Format(0, "0.")
End If
DecimalFlag = True
LastInput = "NUMS"
End Sub

110
' Initialization routine for the form.
' Set all variables to initial values.
Private Sub Form_Load()
DecimalFlag = False
NumOps = 0
LastInput = "NONE"
OpFlag = " "
Readout = Format(0, "0.")

End Sub

' Click event procedure for number keys (0-9).


' Append new number to the number in the display.
Private Sub Number_Click(Index As Integer)
If LastInput <> "NUMS" Then
Readout = Format(0, ".")
DecimalFlag = False
End If
If DecimalFlag Then
Readout = Readout + Number(Index).Caption
Else
Readout = Left(Readout, InStr(Readout, Format(0, ".")) - 1) + Number(Index).Caption +
Format(0, ".")
End If
If LastInput = "NEG" Then Readout = "-" & Readout
LastInput = "NUMS"
End Sub

' Click event procedure for operator keys (+, -, x, /, =).


' If the immediately preceeding keypress was part of a
' number, increments NumOps. If one operand is present,
' set Op1. If two are present, set Op1 equal to the
' result of the operation on Op1 and the current
' input string, and display the result.
Private Sub Operator_Click(Index As Integer)
TempReadout = Readout
If LastInput = "NUMS" Then
NumOps = NumOps + 1
End If
Select Case NumOps

111
Case 0
If Operator(Index).Caption = "-" And LastInput <> "NEG" Then
Readout = "-" & Readout
LastInput = "NEG"
End If
Case 1
Op1 = Readout
If Operator(Index).Caption = "-" And LastInput <> "NUMS" And OpFlag <> "=" Then
Readout = "-"
LastInput = "NEG"
End If
Case 2
Op2 = TempReadout
Select Case OpFlag
Case "+"
Op1 = CDbl(Op1) + CDbl(Op2)
Case "-"
Op1 = CDbl(Op1) - CDbl(Op2)
Case "X"
Op1 = CDbl(Op1) * CDbl(Op2)
Case "/"
If Op2 = 0 Then
MsgBox "Can't divide by zero", 48, "Calculator"
Else
Op1 = CDbl(Op1) / CDbl(Op2)
End If
Case "="
Op1 = CDbl(Op2)
Case "%"
Op1 = CDbl(Op1) * CDbl(Op2)
End Select
Readout = Op1
NumOps = 1
End Select
If LastInput <> "NEG" Then
LastInput = "OPS"
OpFlag = Operator(Index).Caption
End If
End Sub

112
' Click event procedure for percent key (%).
' Compute and display a percentage of the first operand.
Private Sub Percent_Click()
Readout = Readout / 100
LastInput = "Ops"
OpFlag = "%"
NumOps = NumOps + 1
DecimalFlag = True
End Sub

113
 Frm_login

Dim ADOCON As New ADODB.Connection

Dim RS1 As New ADODB.Recordset

Dim RS As New ADODB.Recordset

Private Sub cmdexit_Click()

End

End Sub

Private Sub cmdok_Click()

If txtusername = RS(0) And txtpassword = RS(1) Then

RS1.Open "select Fname,Password from employee where Fname = 'tejas' ", ADOCON

U = RS1.Fields(0)

P = RS1.Fields(1)

If txtusername <> U And txtpassword <> P Then

A = Hour(Time)

If A < 8 Or A > 17 Then

MsgBox "You are not allowed to Log-In to the System before 8:00 AM and after 6:00
PM for Security Reasons", vbOKOnly + vbCritical, "Invalid Log-In"

End

End If

End If

'Label4.Caption = " CORRECT INPUT"

114
frmSplash.Show

Exit Sub

Else

MsgBox "Invalid UserName and Password Entered , Try again ! ", vbOKOnly + vbCritical, "
Login Information"

txtpassword = ""

txtusername = ""

txtusername.SetFocus

End If

End Sub

Private Sub Form_Load()

ADOCON.Open "Provider = Microsoft.Jet.OLEDB.4.0;Data Source=C:\ty\testing.mdb;Persist


Security Info=False"

RS.Open "select Fname,Password from employee", ADOCON

End Sub

115
 Frm_splash

Private Sub Timer1_Timer()

ProgressBar1.Value = ProgressBar1.Value + 1

If ProgressBar1.Value = 100 Then


Unload Me
mdi.Show

116
 Frm_mdi
Private Sub sub_billgen_Click()

frmbillgen.Show

End Sub

Private Sub sub_calculator_Click()

frmCalculator.Show

End Sub

Private Sub sub_calendar_Click()

frmcalendar.Show

End Sub

Private Sub sub_changepswd_Click()

frmchangepswd.Show

End Sub

Private Sub sub_clock_Click()

frmClock.Show

End Sub

Private Sub sub_company_Click()

117
frmCompany.Show

End Sub

Private Sub sub_dealpayment_Click()

frmsup_payment.Show

End Sub

Private Sub sub_emp_Click()

frmEmployee.Show

End Sub

Private Sub sub_order_Click()

frmsup_Order.Show

End Sub

Private Sub sub_paystand_Click()

paystand.Show

End Sub

Private Sub sub_product_Click()

118
frmsup_product.Show

End Sub

Private Sub sub_purchase_Click()

frmsup_purchase.Show

End Sub

Private Sub sub_stock_Click()

stocksumarry.Show

End Sub

Private Sub sub_supdetails_Click()

frmSupplier.Show

End Sub

Private Sub sub_testing_Click()

frmtesting.Show

End Sub

Private Sub sub_testpayment_Click()

frmpayment.Show

119
End Sub

Private Sub sub_tip_Click()

frmtip.Show

End Sub

Private Sub sup_stockselection_Click()

sumarryselection.Show

End Sub

End If

End Sub

120
Chapter 7

SYSTEM
IMPLEMENTATION
AND TESTING

121
SYSTEM IMPLEMENTATION AND TESTING

The installation, delivery and testing of the entire system into production.

Levels of Testing Performed:


Stub test:

A test performed on a subset of a program.

 Individual events or modules of a program are tested.


 Testing of an isolated subset of a program is carried out.

Unit or program test:

A test performed on an entire program.

 All the events and modules are tested as an integrated unit.

Systems test :

A test performed on an entire system

 This test ensures that application programs written and tested in isolation
work properly when integrated into the total system.

Systems acceptance test :

A test performed on the final system wherein users conduct a verification,


validation, and audit test.

 Here we Use real data over an extended time period.


 Extensive test that addresses: verification testing, validation testing, and
audit testing.

122
Verification testing :

Runs the system in a simulated environment using simulated data.

 Alpha testing
 Simulated environment using simulated data
 Checks for errors and omissions regarding end-use and design specifications

123
Chapter 9

CONCLUSION

124
CONCLUSION

The project on “METAL FIRM MANAGEMENT SYSTEM” by now is


familiar to all. I had a great pleasure in developing this project.It is the hard work
has made this out come possible.
I had an hand on experience of operating the various features of the software
tools, which made us aware of the wide future scope. The use of VISUAL BASIC
provided me with the various functions that gave me great ease and convenience in
developing the project.
Working with MICROSOFT ACCESS 2007 has made me know database
operations.
I am very happy to have finally completed the project. It has helped me learn
things that I dould not have learned with the help of books.

125
Chapter 10

BIBILIOGRAPHY

126
 Programming in Visual Basic 6.0
-Julia Bradley

 Software Engineering by Roger Pressman.

 www.microsoft.com
 www.vb6.us

127