CONTENTS

CONTENTS

S.NO DESCRIPTION PAGE NO

1. INTRODUCTION
1.1 ABOUT THE PROJECT 1
1.2 PROFILE OF AN ORGANISATION 3
1.3 OBJECTIVES OF THE STUDY 4
1.4 LIMITATION OF THE STUDY 5
2. SYSTEM SPECIFICATION
2.1 HARDWARE CONFIGURATION 6
2.2 SOFTWARE SPECIFICATION 6
2.3 SOFTWARE DESCRIPTION 7
3. SYSTEM STUDY
3.1 EXISTING SYSTEM 10
3.2 NEED FOR COMPUTERIZATION 11
3.3 DATAFLOW DIAGRAM 12
3.4 PROPOSED SYSTEM 13
3.5 FEASIBILITY STUDY 14
4. SYSTEM DESIGN
4.1 INPUT DESIGN 15
4.2 OUTPUT DESIGN 16
4.3 DATABASE DESIGN 17
5. SYSTEM TESTING AND IMPLEMENTATION
5.1 SYSTEM TESTING 18
5.2 IMPLEMENTATION 22
6. CONCLUSION 23
BIBLIOGRAPHY 24
APPENDIX
A. FORMS 25
B. SAMPLE CODING 33
C. TABLE STRUCTURE 37
D. REPORTS 39
INTRODUCTION
 1. INTRODUCTION

1.1 ABOUT THE PROJECT

This Project is entitled “KNITTING MANAGEMENT SYSTEM” AT MUTHUVEL

KNITS is Windows Application software with Visual Basic 6.0 as front end and MS
ACCESS as back end used to manage the resource to the full extend.

This project main aim is to computerized the processing of the yarn. This project
helps to collect and maintain the information about buyers details, supplier, order, and stock
details with daily reports. Thread or yarn may be turned into cloth or other fine crafts.
Knitting consists of consecutive loops and called stitches.

This project advantage of the system is user friendly and GUI development. The
record navigation is done using list view control of visual basic, user can just pick or click the
contents they need to view or modified. They can add new record or modify from the existing
records.

1
DESCRIPTION OF MODULES
We had to build the system so that it shows the following information
 Login details
 Buyer details
 Supplier details
 Employee details
 Stock details
 Order details

LOGIN DETAILS:
In this module contains of information of login details username and password.

BUYER DETAILS:
In this module contains Add new buyer and his address, country, phone no, Also
check if others are active.

SUPPLIER DETAILS:
In this module contains of supplier name , address, date of birth, gender.

EMPLOYEE DETAILS:
In this module contain of employee name address and phone no, designation, salary.

STOCK DETAILS:
It contains of item id, item name, purchase quantity, sales quantity, stock in hand.

ORDER DETAILS:
In this modules contains company name, design, color, order date

2
1.2 PROFILE OF AN ORGANIZATION

NAME OF THE ORGANISATION : MUTHUVEL KNITS

PARTNER NAME 1 : VISHNU

MANAGER NAME : GOVIDHARAJ

YEAR OF THE ESTABLISHMENT : 2010

CAPITAL OF THE ORGANISATION : 600000

WORKERS/STAFFS : 15

ADDRESS/CONTACT : SF.254, VELAMPALAYAM RING ROAD

15. VELAMPALAYAM, TIRUPUR, INDIA

PHONE NO : 914212484877

E-MAIL : fabrication@muthuvel.com

3
1.2 OBJECTIVES OF THE STUDY

 The main objective is to computerize all the manual process in the organization.

 To store buyer details, size and color of fabrics.

 To reduce mistake of records.

 To enable quick processing of searching of knitting process.

 To maintain proper and up to data records of all transaction.

4
1.3 LIMITATION OF THE STUDY

 This output depends upon quality of input.

 The form designing and the coding are based on the information given by the concern.

5
SYSTEM SPECIFICATION
 2. SYSTEM SPECIFICATION

2.1 HARDWARE SPECIFICATION

Processor : Intel core 2 duo 2.4 GHz

Ram : 1 GB DDR2 ram

Monitor : 15” color

Hard disk : 80 GB

CD Dive : 1g 52x

Keyboard : standard 102 keys

Mouse : Optical mouse

2.2 SOFTWARE SPECIFICATION

Front-End : Microsoft Visual Basic 6.0

Back-End : MS- Access 2007

Operating System : Windows 7

6
2.3 SOFTWARE DESCRIPTION

FRONTEND

Introduction to Visual Basic

Visual Basic is a programming language and development environment created by

Microsoft. Visual Basic provides a graphical user interface GUI that allows the developer
drag and drop objects into the program as well as manually write program code. Visual Basic,
also referred to as "VB," is designed to make software development easy and efficient

Visual Basic 6.0

 Visual Basic is a programming language and integrated development environment.

 It derives from the much older BASIC programming language, and so is considered
useful and easy programming language for the beginner to learn.
 Visual Basic 6.0 was the final edition of Visual Basic.

FEATURES

 Learning Consists of all necessary tools required to build main stream

Windows Applications
 Professional Includes advanced features such as tools to develop ActiveX and Internet
controls.
 Enterprise In addition to all Professional features, it also includes tools such as Visual
basic6.0

7
Features of visual basic
 GUI Interface
 Modularization
 Object Oriented
 Debugging
 Macros IDE
 Data access feature

GUI Interface: - VB is a Graphical User Interface language. This means that a VB

program will always show something on the screen that the user can interact with to get a job
done.

Modularization: - It is considered good programming practice to modularize your

programs. Small modules where it is clearly indicated what comes into the module and what
goes out makes a program easy to understand.

Object Oriented: - Object Oriented Programming is a concept where the

programmer thinks of the program in "objects" that interact with each other. Visual Basic
forces this good programming practice.

Debugging: - Visual Basic offers two different options for code debugging:-
Debugging Managed Code Runtime Debugger The Debugging Managed Code individually
debugs C and C++ applications and Visual Basic Windows applications. The Runtime
Debugger helps to find and fix bugs in programs at runtime.

Data Access Feature: - By using data access features, we can create databases,
scalable server-side components for most databases, including Microsoft SQL Server and
other enterprise-level database.

8
 Macros IDE: - The Macros integrated development environment is similar in design
and function to the Visual Studio IDE. The Macros IDE includes a code editor, tool windows,
the properties windows and editors.

Definition - What does Microsoft Access mean?

Microsoft Access is a pseudo-relational database engine from Microsoft. It is part of
the Microsoft Office suite of applications that also includes Word, Outlook and Excel, among
others. Access is also available for purchase as a stand-alone product. Access uses the Jet
Database Engine for data storage.

Access is used for both small and large database deployments. This is partly due to its
easy-to-use graphical interface, as well as its interoperability with other applications and
platforms such as Microsoft’s own SQL Server database engine and Visual Basic for
Applications (VBA).

Techopedia explains Microsoft Access

The Access Jet engine supports most database features, such as referential integrity,
row-level locking and multiuser support with up to 255 concurrent user connections. Access
is well-suited for creating small databases such as those used by single departments. It is not
suitable for larger, enterprise-level databases. For these, Microsoft offers its SQL Server
database engine.

Access was first released as version 1.0 in November 1992. The software was fine
while working with small databases but in larger files there was the danger of data corruption.
With each release of Office, Microsoft has also included a newer version of Access, each of
which includes new or updated features.

With the release of Access 2007, the database file format changed from the previous
".mdb" to ".accdb" This new format supports more complex data types, but unfortunately is
not compatible with prior versions of the Access software. This is analogous to the new
".docx" and ".xlsx" formats in Word and Excel, which are also incompatible with the pre-
2007 versions of these programs.

9
SYSTEM STUDY
 3. SYSTEM STUDY

3.1 EXISTING SYSTEM

In this concern, data increases rapidly day by day, it is hard to continue as a manual
system. The volume of data available is growing day by day, maintaining the details in
Manual Files and Accessing the information from it makes the job more complicated and
wastes the manpower. When human handles the huge data, few mistakes may occur.The
existing system is maintained manually. In the present system whenever the customer gives
an order it is maintained manually in the notebook. Manually they have to update the
Production Order, Production Plan of items, Production Monitoring etc. So the present
system is not good enough for the company

3.1.1 DRAWBACKS OF EXISTING SYSTEM

 File maintenance is extremely difficult as everything is done manually.

 Information retrieval is difficult and time consuming.

 Quick analysis of delivery is not possible.

 Not enough security and privacy.

 Requires much human effort.

10
3.2 NEED FOR COMPUTERIZATION

Computers are one of the most important tools between peoples in everyday life.
One would find it very difficult to live without computers. If computer all over the world
come to a half or stand still, it would be like the earth has stopped revolving. Computer is
must in today’s life. No matter what application it is, a computer assisted system is much
more beneficial than the manual system. its need arises from the benefits of speed, accuracy
and lower cost of handling the business transactions. Also, it has the capability to record a
large number of transactions with speed and accuracy.

11
3.3 DATAFLOW DIAGRAM

LOGIN

Buyer
Details
SUPPLIER
SUPPLIER

DETAILS
Sup_Datas Add, Delete, Save, Edit

ORDER ORDER
DETAILS
Order_Datas Add, Delete, Save, Edit

DELIVERY
DELIVERY
/ STOCK
STOCK

Stock_Datas Add, Delete, Save, Edit

EMPLOYEE EMPLOYEE

Emp_Datas Add, Delete, Save, Edit

REPORT

12
3.4 PROPOSED SYSTEM

The proposed “KNITTING MANAGEMENT SYSTEM” is developed to automate

all the outgoing stocks of the company. The proposed system makes the job easier and more
convenient. The user friendliness of the new system makes it to be operated even by a naive
user. The information retrieval is fast needed security and privacy has been provided. The
chances of inaccuracy are nil. Hence the newly developed computerized system is far better
than the old manual system. This new system updates all related table automatically. The user
friendliness of the new system makes it to be operated even by a naïve user. The information
retrieval is fast needed security and privacy has been provided. The chances of inaccuracy are
nil. Hence the newly developed computerized system is far better than the old manual
system.

3.4.1 FEATURE

 The feedback from early increments can influence the later stages.

 Users get benefits earlier. The users will have an idea of the system as and when

implemented.

 Smaller subprojects are easier to control and manage.

 Keep track of errors in each increment and solved as and when founded.

 Less Cost Estimation

13
3.5 FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system analysis
the feasibility study of the proposed system is to be carried out. This is to ensure that the
proposed system is not a burden to the company. For feasibility analysis, some understanding
of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY
This study is carried out to check the economic impact that the system will have on
the organization. The amount of fund that the company can pour into the research and
development of the system is limited. The expenditures must be justified. Thus the developed
system as well within the budget and this was achieved because most of the technologies used
are freely available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed system
must have a modest requirement, as only minimal or null changes are required for
implementing this system.

SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system
and to make him familiar with it. His level of confidence must be raised so that he is also able
to make some constructive criticism, which is welcomed, as he is the final user of the system.

14
SYSTEM DESIGN
 4. SYSTEM DESIGN

4.1 INPUT DESIGN

Input design is the process of converting the user-oriented description of the computer
based business information into program-oriented specification. The goal of designing input
data is to make the automation as easy and free from errors as possible. Input Design
considered the following things:

INPUT FORMS:

 Log in details form

 Buyer details form
 Supplier details form
 Employee details form
 Stock details form
 Order details form

15
4.2 OUTPUT DESIGN

Output Design is the most important and direct source of information to the user. The
output design is an ongoing activity during study phase. The objectives of the output design
define the contents and format of all documents and reports in an attractive and useful format.
The main output generated here is the reports. The reports were generated for
selective reasons. The various generated are as follows

OUTPUT REPORT:

 Log in details report

 Buyer details report
 Supplier details report
 Employee details report
 Stock details report
 Order details report

16
4.3 DATABASE DESIGN

A database is a collection of interrelated data stored with minimum redundancy to

serve many users quickly efficiently. The general objective is to make information access
easy and flexible for the users. In Access we can create database and the tables for sorting
data. Database design is based on several objectives such as controlled redundancy, easy of
learning and use, data independence, more information at low cost, accuracy and integrity,
recovery from failure, security and enhanced performance.
In this system Access is used to create database. Access provides easy way to access
database. It is easy to create table and store information to the tables. The most important
consideration in designing the database is how information will be used. The main objectives
of designing a database are:

DATA INTEGRATION:
In a database, information from several files are coordinated, accessed and operated
upon as through it is in a single file. Logically, the information are centralized, physically, the
data may be located on different devices, connected through data communication facilities.

DATA INTEGRITY:
Data integrity means storing all data in one place only and how each applications to
access it. This approach results in more consistent information, one update being sufficient to
achieve a new record status for all applications, which use it. This leads to less data
redundancy; data items need not be duplicated; a reduction in the direct access storage
requirement.

DATA INDEPENDENCE:
Data independence is the insulation of application programs from changing aspects of
physical data organization. This objective seeks to allow changes in the content and
organization of physical data without reprogramming of applications and to allow
modifications to application programs without reorganizing the physical data. The tables
needed for each module were designed and the specification of each and every column was
given based on the records and details collected during record specification of the system
study.

17
SYSTEM TESTING AND
IMPLEMENTATION
 5. SYSTEM TESTING AND IMPLEMENTATION

5.1 SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the Software system meets its
requirements and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.

TYPES OF TESTING:
UNIT TESTING
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application. it is done after the completion of an individual unit before
integration. This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration. Unit tests ensure that each unique path of a
business process performs accurately to the documented specifications and contains clearly
defined inputs and expected results.

INTEGRATION TESTING:
Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.

18
FUNCTIONAL TEST

Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and user
manuals.

Functional testing is centred on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key

functions, or special test cases. In addition, systematic coverage pertaining to identify
Business process flows; data fields, predefined processes, and successive processes must be
considered for testing. Before functional testing is complete, additional tests are identified
and the effective value of current tests is determined.

SYSTEM TEST

System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results. An example of system testing
is the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

19
WHITE BOX TESTING
White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.

BLACK BOX TESTING:

Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most other
kinds of tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.

UNIT TESTING:
Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

TEST STRATEGY AND APPROACH

Field testing will be performed manually and functional tests will be written in detail.

TEST OBJECTIVES
 All field entries must work properly.
 Pages must be activated from the identified link.
 The entry screen, messages and responses must not be delayed.

FEATURES TO BE TESTED
 Verify that the entries are of the correct format
 No duplicate entries should be allowed
 All links should take the user to the correct page.

20
INTEGRATION TESTING:
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications,
e.g. components in a software system or – one step up – software applications at the company
level – interact without error.

TEST RESULTS:
All the test cases mentioned above passed successfully. No defects encountered.

ACCEPTANCE TESTING
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

TEST RESULTS:
All the test cases mentioned above passed successfully. No defects encountered.

21
5.2 IMPLEMENTATION

Implementation is the stage of the project when the theoretical design is turned out
into a working system. Thus it can be considered to be the most critical stage in achieving a
successful new system and in giving the user, confidence that the new system will work and
be effective.

The implementation stage involves careful planning, investigation of the existing

system and it’s constraints on implementation, designing of methods to achieve changeover
and evaluation of changeover methods.

22
CONCLUSION
 6. CONCLUSION AND FUTURE ENHANCEMENT

This project is entitled knitting management system at Muthuvel knits is developed

using visual basic 6.0 has its front end and Microsoft access has back end. It may be stored
and referred in the future for the concern with the modern technological enhancement. This
software developed has been designed and run to satisfy the requirement and needs of the
management as well as end uses. This system reduces the manual work of maintenance of the
records. It has also result in quick retrieval and reference of required information, which is
vital to the degrees of the management.

Knitting Management System will help the garments industries to work effectively
with their buyers and bring great success to their business. The goal of the project has been
successfully achieved. The testing and implementation has been done in a step-by-step
process. Each module has been developed and tested individually to obtain the necessary
required output in the desired form.

23
BIBLIOGRAPHY
 BIBLIOGRAPHY

BOOKS REFERRED

 Visual Basic 2008 Programmer's Reference Book by Rod Stephens

 Visual Basic 2015 Unleashed Book by Alessandro Del Sole
 Visual Basic 2010 Programmer's Reference Book by Rod Stephens
 Alex Homer , “Professional VB”, 2004 Edition, Wrox Publications
 Steven Holzner, “Visual Basic Black Book”, 2003 Edition, Dreamtech Publications
 Roger S Pressman, “Software Engineering”, 2000 Edition, Dreamtech Publications
 Visual Basic 2012 Programmer's Reference Book by Rod Stephens
 Visual Basic 6: The Complete Reference (With Cd) Book by Noel Jerke

WEBSITES REFERRED

 www.msdn.microsoft.com
 www.vbcity.com
 www.freevbcode.com
 www.a1vbcode.com
 www.codeguru.com
 www.w3schools.com.
 www.vbcode.com
 www.visualbasic6class.com
 www.example-code.com/vb6
 www.planet-source-code.com/vb/

24
APPENDIX
 APPENDIX

A.FORMS

LOG IN FORM

25
ADMIN FORM

26
MDI FORM

27
BUYER DETAILS FORM

28
SUPPLIER DETAILS FORM

29
EMPLOYEE DETAILS FORM

30
STOCK DETAILS FORM

31
ORDER DETAILS FORM

32
B. SAMPLE CODING
LOG IN DETAILS
Private Sub CMDSUBMIT_Click()
If Text1.Text = "admin" And Text2.Text = "admin" Then
MsgBox "login successfully", vbInformation, "login"
Form1.Hide
Form2.Show
ElseIf Text1.Text = "user" And Text2.Text = "user" Then
MsgBox "login successfully", vbInformation, "login"
Form1.Hide
Form2.Show
Else
MsgBox "login failed", vbCritical, "login"
End If
End Sub
MDI FORM
Private Sub A_Click()
Form4.Show
End Sub
Private Sub B_Click()
Form5.Show
End Sub
Private Sub C_Click()
Form9.Show
End Sub
Private Sub D_Click()
Form7.Show
End Sub
Private Sub E_Click()
Form8.Show
End Sub

33
Private Sub G_Click()
DataEnvironment1.Command1
DataReport1.Show
End Sub
Private Sub H_Click()
DataEnvironment1.Command2
DataReport2.Show
End Sub
Private Sub I_Click()
DataEnvironment1.Command3
DataReport3.Show
End Sub
Private Sub J_Click()
DataEnvironment1.Command4
DataReport4.Show
End Sub
Private Sub K_Click()
DataEnvironment1.Command5
DataReport5.Show
End Sub
Private Sub L_Click()
End
End Sub
BUYER DETAILS
Private Sub CMDADD_Click()
Data1.Recordset.AddNew
MsgBox "added"
End Sub
Private Sub CMDDELETE_Click()
Data1.Recordset.Delete
MsgBox "deleted"
End Sub
Private Sub CMDEND_Click()
End
34
End Sub
Private Sub CMDSAVE_Click()
Data1.Recordset.Update
MsgBox "save done"
End Sub
SUPPLIER DETAILS
Private Sub CMDADD_Click()
Data1.Recordset.AddNew
MsgBox "added"
End Sub
Private Sub CMDDELETE_Click()
Data1.Recordset.deleted
MsgBox "deleted"
End Sub
Private Sub CMDEND_Click()
End
End Sub
Private Sub CMDSAVE_Click()
Data1.Recordset.Update
MsgBox "saved"
End Sub
EMPLOYEE DETAILS
Private Sub CMDADD_Click()
Data1.Recordset.AddNew
MsgBox "Added"
End Sub
Private Sub CMDDELETE_Click()
Data1.recoerset.deleted
masgbox "deleted"
End Sub
Private Sub CMDSAVE_Click()
Data1.Recordset.Update
MsgBox "save done"
End SubPrivate Sub CMDEND_Click()
35
End
End Sub
STOCK DETAILS
Private Sub CMDADD_Click()
Data1.Recordset.AddNew
MsgBox "added"
End Sub
Private Sub CMDCALCULATE_Click()
Text5.Text = Val(Text3.Text) - Text4.Text
End Sub
Private Sub CMDEND_Click()
End
End Sub
Private Sub CMDSAVE_Click()
Data1.Recordset.Update
MsgBox "saved"
End Sub
ORDER DEATAILS
Private Sub CMDADD_Click()
Data1.Recordset.AddNew
MsgBox "added"
End Sub
Private Sub CMDEND_Click()
End
End Sub
Private Sub CMDSAVE_Click()
Data1.Recordset.Update
MsgBox "saved"
End Sub
Private Sub CMDDELETE_Click()
Data1.Recordset.Delete
MsgBox "DELETED"
End Sub

36
C. TABLES STRUCTURE

TABLE NAME: BUYER DETAILS

FILED NAME DATA TYPE SIZE

Buyer id Integer 10
Buyer name Text 20
Buyer address Text 100
Phone no Integer 10

TABLE NAME: SUPPLIER DETAILS

FIELD NAME DATA TYPE SIZE

Supplier id Integer 10
Supplier name Text 50
Supplier address Text 100
Phone no Integer 10
Date of birth Integer 10
Gender Text 50

TABLE NAME: EMPLOYEE DETAILS

FIELD NAME DATA TRYPE SIZE

Employee name Text 50
Employee id Integer 10
Employee address Text 100
Phone no Integer 10
Designation Text 50
Salary Integer 10
Date of join Integer 10

37
 TABLE NAME: STOCK DETAILS

FIELD NAME DATA TYPE SIZE

Product id Integer 10
Product name Text 50
Purchase quantity Integer 20
Sales quantity Integer 10
Stock in hand Integer 10

TABLE NAME: ORDER DETAILS

FIELD NAME DATA TYPE SIZE

Company name Text 50
Color Integer 10
Design Integer 10
Order date Integer 10

38
D. REPORTS

BUYER DETAILS REPORT

39
SUPPLIER DETAILS REPORT

40
EMPLOYEE DETAILS REPORT

41
STOCK DETAILS REPORT

42
ORDER DETAILS REPORT

43