DESIGN AND IMPLEMENTATION OF AN ELECTRONINC

INVOICING SYSTEM

For Application Source Code, Visit

https://software.ng/softwares/inventory.zip

ii
 ABSTRACT

This research work is concise and generally summarizes the activities duly

carried out in the design and implementation of an electronic invoicing system

in Gamzaki store. The system is designed to efficiently handle the movement and

tracking of goods through the replacement of human workers by technology.

The manual method or intervention is labour intensive, costly, and error prone

and cannot ensure the inventory remains up-to-date due to oversight and

internal shrinkage. With the proposed new system, inventory can be updated in

real time without product movement, scanning, or human involvement. The

automated system allows inventory status to be determined and shipping and

receiving documents to be generated automatically triggering automatic orders

for products that are low in inventory. The study outlines the main concepts of

the analysis and design methodology of the proposed system, compares it to the

existing and goes further to explain the design and implementation of the system

using MS Access for the database. The fact finding techniques employed is

interview, observation, online and library research.

iii
iv
 TABLE OF CONTENT

Title Page ---------------------------------------------------------------------------------- i

Approval Page --------------------------------------------------------------------------- ii

Acknowledgement ---------------------------------------------------------------------- iii

Dedication ------------------------------------------------------------------------------- iv

Abstract ----------------------------------------------------------------------------------- v

Table of Content-------------------------------------------------------------------- vi-viii

Chapter One: Introduction

1.1 Introduction ----------------------------------------------------------------------- 1-2

1.2 Problem Statement ------------------------------------------------------------------ 2

1.3 Aim of Project ----------------------------------------------------------------------- 3

1.4 Objectives ---------------------------------------------------------------------------- 3

1.5 Scope of the Project -------------------------------------------------------------- 3-4

1.6 Limitation of the Project ----------------------------------------------------------- 4

Chapter Two: Literature Review

2.1Review of Related Literature ---------------------------------------------------- 5-6

2.2 Description of the topic ------------------------------------------------------------ 6

2.3 Brief History of Case Study ------------------------------------------------------- 7

Chapter Three: System Analysis and Design

3.1 Analysis ---------------------------------------------------------------------------- 8

v
3.2 System Investigation Procedure ------------------------------------------------- 8

3.3 Description of Existing System -------------------------------------------------- 8

3.4 Analysis of the Existing System ------------------------------------------------ 9

3.5 Problems associated with existing system ------------------------------------- 10

3.6 Advantage of the New System -------------------------------------------------- 11

3.7 Need to the Automation of Inventory Control System ------------------ 11-13

3.8 Processes in the Automation of Inventory Control System ----------------- 13

3.9 System Design --------------------------------------------------------------------- 14

3.9.1 Structure Chart ------------------------------------------------------------------- 15

3.9.2 Use Case Diagram --------------------------------------------------------------- 16

3.10 Database Design ------------------------------------------------------------------ 17

3.11 Design Process ------------------------------------------------------------------- 17

3.11.1 Input Specification --------------------------------------------------------- 18-19

3.12 Output Specification ------------------------------------------------------------ 19

3.8.3 Processing ------------------------------------------------------------------------ 20

3.8.4

Chapter Four: System Implementation

4.1 Implementation Stages ------------------------------------------------------------ 21

4.1.1 Programming Stage ------------------------------------------------------------- 21

4.1.2 User Training Stage ------------------------------------------------------------- 21

4.2 System Requirements ------------------------------------------------------------- 22

4.2.1 Software Requirements --------------------------------------------------------- 22

vi
4.2.2 Hardware requirement ---------------------------------------------------------- 22

4.2.3 Input Requirement/Specification ---------------------------------------------- 23

4.2.4 Output Requirement/Specification -------------------------------------------- 23

4.2.5 Non Functional Requirements ------------------------------------------------- 23

4.3 Implementation ---------------------------------------------------------------- 24-28

4.4 System Testing -------------------------------------------------------------------- 28

4.5 System Integration ---------------------------------------------------------------- 28

4.6 Operating the New System ------------------------------------------------------- 29

4.7 Error handling ---------------------------------------------------------------------- 29

Chapter Five: Summary, Conclusion and Recommendation

5.1 Summary ---------------------------------------------------------------------------- 30

5.2 Recommendation ------------------------------------------------------------------ 30

5.3 Conclusion ------------------------------------------------------------------------- 31

References -------------------------------------------------------------------------- 32-33

Appendix ---------------------------------------------------------------------------- 34-44

vii
 CHAPTER ONE

INTRODUCTION

1.1 BACKGROUND OF THE STUDY

Electronic invoicing System is the process of managing inventory in

order to meet customer demand at the lowest possible cost and with a minimum

investment, Byoungho (2004). A successfully implemented invoicing control

program takes into account such things as purchasing goods commensurate with

demand, seasonal variation, changing usage patterns, and monitoring for

pilferage, Ellram (1996). A preliminary step in the process of invoicing control

is to determine the approximate costs of managing invoice. According to

Langabeer and Stoughton (2001), these costs include such expenses as storage

costs, inventory risks, and the loss-of opportunity costs associated with tying up

capital. Inventory management is a vital function to help ensure the success of

manufacturing and distribution companies and lately retail stores. The

effectiveness of invoicing management systems is directly measurable by how

successful a company is in providing high level of customer service, low

inventory investment, maximum throughput and low costs, Ellram (1996). The

challenge of productive invoicing management is to support an upward trend in

sales while keeping the investment at the lowest level consistent with adequate

customer service. Control of invoice, which typically represents 45% to 90% of

all expenses for business, is needed to ensure that the business has the right
goods on hand to avoid stock-outs, to prevent shrinkage (spoilage/theft), and to

provide proper accounting, Khan (2003).

Articles stored and later used in this way are known collectively as

inventory. In large organizations, it is usual for inventory to be in tens, even

hundreds of items valued at tens of millions of naira. Given this state, it has

become natural to have inventory items represented in computer maintained

files. Computer especially microcomputer has become an important tool in all

types of business from one man operations up to large international business

firms.

Every business manager need to know what he purchased, what he sold

and what is remaining in the warehouse. For this obvious reason, large, small

and medium organizations, companies and government, as a whole need

computerization of inventory control. The speed at which the administrative and

paper work in retail stores increases on daily basis calls for a corresponding

need for a quick and effective device to meet up with the demand. This project

hopes to link inventory control and computer system.

1.2 PROBLEM STATEMENT

The current inventory control at Gamzaki store is completely manual

which result in inaccuracy and inefficiency in record keeping of availability or

otherwise of goods in the store. The process of updating the inventory requires

the sales personnel to monitor stock level of each item. Anytime a stock level
reaches a point that is too high or low, an action is instituted which include to

write down stock status report or to generate a purchase order. There are a lot of

problems associated with using this manual method which include time wasting,

difficulty in calculating the total amount of items sold, too much paper work

and difficulty in updating every time a change is made, hence the need for

automating the inventory system.

The proposed automated system will take in data of stock items like stock

number, product name, quantity, cost price and selling price as inputs. The

system process and update records accurately within a short time and store it.

After processing these inputs, the system will be able to generate sales report,

stock report, payment receipt and transactions history report as outputs.

The new system will be able to generate report regarding the details of

stocks available in the store and print out the various reports generated via a

printer. Also, security provision like the login authenticity will be provided so

as to curtail unauthorized access to the system.

1.3 AIM OF THE PROJECT

The main aim of this project is to develop software that will automate the

current manual invoice control system through incorporation of computer to

eliminate errors relating to inventory control calculations and management.

1.4 OBJECTIVES
 i. To provide system that keeps constant updates about total number of

stock available in the store and constantly each and every items in the

stock that is going down low to out of stock, the system alert as soon as is

due.

ii. To provide software that save time and reduces energy consumption by

making complicated processing and inventory sales report easy and

without delay.

iii. To help track sales, hence staffs are constrained to sell at a fixed price

and remit recommended price.

iv. To be able to discover several goods in stock that are about to expire in

stock. The software gives the flexibility to know every single item in the

store, its Quantity and their expiry dates at just a click to the software.

v. The software provide easy way to print out weekly/monthly summary

reports, showing how much have been used for different stock items from

a computerized stock system.

1.5 SCOPE OF THE PROJECT

The program is designed to take care of a typical control system, which

deals with invoice control of Gamzaki Store and other retail stores/supermarkets

alike having similar problem of inventory control.

1.6 LIMITATION OF THE PROJECT

 The study was faced with a problem of getting all the information from

the respondent because of potential cynical suspicion. Poor keeping of records

caused some data not to be available and finally some respondent were not able

to give the desired responses as they were not much familiar with adequate

knowledge on invoice management.

1.7 Definition of Terms

i. Item Name: - This is a name given to each product. This name is unique to

the product by which it identifies.

ii. Stock Balance : - This is the number of goods that are present in stock

iii. Cost Price: - This is the initial cost of purchased goods

iv. Selling Prices: - This is the cost at which goods or a particular item is sold

after being purchased.

v. Receipt: - This is a document prepared to be given out to a customer for

confirmation of goods purchased.

vi. Transaction History: - it is used to show all the list of daily sales and

stored each record for reference purpose.

vii. Change Password: - it allows the management or system admin to change

a password.
viii. Low Stock Balance Alert: - it is a reminder that keeps you updated

whenever a stock balances is going down or low.

 CHAPTER TWO

LITERATURE REVIEW

2.1 REVIEW OF RELATED LITERATURE

Graman and Magazine (2006), argued that today, the cost of holding

inventory, extensive product proliferation and the risk of obsolescence,

especially in rapidly changing markets, make the expense of holding large

inventories of finished goods excessive and that high demand items naturally

have safety stock assigned to them, but in many organizations there are so many

very-low-demand items that keeping any stock of these items is unreasonably

expensive, so they argue that companies must now provide good service while

maintaining minimal inventories. Therefore, invioce control system approaches

are essential aspects of any organization. Wallin et al. (2006), has argued that

that a typical manufacturing firm spends on average, 56 cents out of every

dollar of revenue to cover the direct cost of purchased goods, and Monczka et

al. (2002), and Handfield (2002), have argued that this percentage figure is

higher for the typical wholesaler or retailer. Therefore, organizations from

manufacturing to wholesale to retail require effective invoice control system.

Invoice control systems have been of concern for many years to business

firms worldwide. Inventory control systems play a crucial role in enhancing

effectiveness and efficiency in handling inventory of business firms. Companies

have been continually in search for sources of sustainable competitive

advantage in their operations. Therefore, there is need for business enterprises

to embrace effective inventory management practices in order to improve their

competitiveness (Rajeev, 2008). In 1980s inventories of raw materials, work-in-

progress components and finished goods were kept as a buffer against the

possibility of running out of needed items (Salawati, Tinggi, & Kadri, 2012).

However, large buffer inventories consume valuable resources and generate

hidden costs (Salawati, Tinggi, & Kadri, 2012). Too much invoice consumes

physical space, creates a financial burden, and increases the possibility of

damage, spoilage and loss (Nyabwanga & Ojera, 2012). On the other hand, too

little inventory often disrupts business operations (Dimitrios, 2008).

Lyson (1996) posits that invoice control enhances profitability by

reducing costs associated with storage and handling of materials. According to

Buffa and Salin (1987) there are several reasons for keeping inventory. Too

much stock could result in funds being tied down, increase in holding cost,

deterioration of materials, obsolescence and theft. On the other hand, shortage

of materials can lead to interruption of products for sales; poor customer

relations and underutilized machines and equipments.

2.2 DESCRIPTION OF THE TOPIC

Automation of invoice control is hoped to be achieved with the aid of

using a computer for stock control in a retail stores. The computerized system

will be aided with a program installed into the computer that will be capable of
preparing or taking stock of various items with different prices, most of which

are too cumbersome especially to organization with large quantity of items. The

program will be designed in a way that it can take the stock number, product

name, description and selling price of each item. The computerization of the

system is not to alter but to change the manual procedures or method to a

computerized one.

In this research, inventory control is seen as a term which implies a step

taken by an organization or a retail stores that deals with various types of item,

to calculate their quantity in stock, cost price and selling price. The

computerized invoice control system is hope to be more convenient for any

organization or retail stores because it has reasonable level of accuracy and

reliability of data processing method which involves input, process and output.

2.3 BRIEF HISTORY OF CASE STUDY

Gamzaki Store was started as small retail store at Habibu Gwarzo Street

Hotoro Nasarawa, Kano in the year 1990 by Alhaji Ali Sa’ad who is the

manager since its inception. As it is common with small business startups, it

started with few goods in stock but three years later Gamzaki had to move to a

place more spacious near the one it was occupying because of growth in the

business. By 1998 it had to move to its present location still on Habibu Gwarzo

street, in order to accommodate more stocks. Also, the following year as the

small startup developed into big time retail chain stores as it opened another big
shop at Nigerian law School, Bagauda. The store deals in goods ranging from

fast food, electronics, shoes, clothes, jewellery, cosmetics, stationary, kiddies

and many more that normally general stores trade in.

CHAPTER THREE

SYSTEM ANALYSIS AND DESIGN

3.1 ANALYSIS

This involves the specification of procedures for collecting and analyzing

data necessary to define or solve the problem for which the research is

embarked upon. This chapter describes the method employed in carrying out the

research project on automation the of inventory control system of Gamzaki

Store, Habibu Gwarzo Street, Hotoro, Kano.

3.2 SYSTEM INVESTIGATION PROCEDURE

This project was achieved by gathering materials from different sources.

One of the invaluable sources of data was oral interview, which I conducted

with stake holders in Gamzaki Store.

3.3 DESCRIPTION OF THE EXISTING SYSTEM

In the manual system of computing the data of each item in Gamzaki

Store, it starts or begins with the stock number, the product name, quantity in

stock, cost price, selling and re - order level in order to ascertain the accuracy

and proper stock taking. To keep track of their inventory levels they have to

calculate a list of the groceries utilized during a course of time, calculate and

analyze the requirements for the future, and place their next order to the vendors

if needed. This process takes up a lot of time and human effort, and is also

prone to human error.

This poses a problem of a situation that the staff at Gamzaki Store as well

as many other stores faces. It takes up a lot of time to manually keep track of
sales and place correct orders to vendors, wasting useful labor on trivial works.

A software which can assist in tackling the above mentioned problems would

prove to be fruitful to Gamzaki Stores and similar enterprises as it would help

convert unproductive time to something more useful, by removing the

unnecessary error prone complications and efforts.

3.4 ANALYSIS OF THE EXISTING SYSTEM

The existing system is one that has been manually operated over the

years. It is a system in which all the methods of controlling inventory is of

manual approach. Critical analysis of this system reveals that it is prone to

errors. Careful analysis also shows that due to the complexities of the manual

system, records of invoice kept are inaccurate and manually operated in such a

way that requires the clerk to register sales on a book, thereby making a staff

handle two or three jobs at a time. An example is a staff trying to register sales

and at the same time rushing back to face a queue of impatient customers

waiting to be attended to. This makes the place so crowded with customers with

just one person attending to them. Sometimes, due to unavailability of staff,

customers who have other things to do, end up missing their various

appointments. As a result of this, the attendant finds it very difficult to have an

accurate record as pressure is being mounted on him. Gamzaki Store operates

manually and has not adopted an Automation mode of operation. This generates
inadequate records or exercise improper management of the store and in

extreme cases, the store may lose its customers.

3.4.1 FLOW CHART OF THE EXISTING SYSTEM

3.5 PROBLEMS ASSOCIATED WITH EXISTING SYSTEM

The existing system in Gamzaki Store lacks the efficiency and flexibility

in handling of data relating to invoice control of its items. Below are some of

the problems outlined;

a) Old method of operations

b) Repetition of routines
 c) Difficulty in updating when new stocks are added

d) Wrong calculation

3.6 ADVANTAGE OF THE NEW SYSTEM

1. Speed and Efficiency

A computerized invoice management system makes everything from inputting

information to taking inventory easier. Doing a hand count of inventory can

take days, but with a computerized invoice management system, the same

process can be done in a matter of hours.

2. Document Generation

Once the computerized invoice management system is in place, managers and

workers can use it to automatically generate all kinds of documents, from

purchase orders and checks to invoices and account statements. Managers can

also use the system to automatically order products when they run low.

3. Timely Data

With a manual system, the data is only as accurate and up to date as the last

hand count. With a computerized invoice management system, the management

team can pull a report and instantly see how many units are on the floor, how

many have sold and which products are selling the fastest.
3.7 NEED FOR THE AUTOMATION OF INVENTORY

CONTROL SYSTEM

a. One way of checking the stock in Gamzaki is to go to stock warehouse

and count what is there. This is unsuitable for a big shop. A better

approach is to set up one information system to record what we have in

the stock.

b. By using computer system instead of manual system, time is saved and

cost because the time spent in updating a computer is likely to be less

than a manual system. Application of computer hence therefore, implies

the computerization of the entire invoice control system of Gamzaki so as

to derive maximum benefits.

c. Better management control and better management of information.

d. With the computer system being used to keep accurate and up to date

records which will prevent theft and easy way operation to the super

markets staff or workers unlike the manual system.

e. Using computers is easy and possible to print out weekly/monthly

summary reports, showing how much has been used for different stock

items from a computerized stock system.

f. It will constantly keep update about total numbers of stock available in

the inventory and when any item in the stock is going down low to out

of stock, the system alert as soon as is due.

g. It gives the flexibility to generate and print automatic receipt when any

item is purchased from the store.

h. The software will help to track sales, sales personnel are also constrained

to sell at a fixed price and remit recommended price.

i. A third party or your staff may steal from you; a system must be place to

implement controls and accountability. Nothing surpasses a properly

implemented combination of computer hardware, requisite software and a

foolproof set of business rules or operating policies.

j. As invoices are sent to the printer from the system, sales records are

automatically updated as are Invoice balances. A single transaction

updates core database. With your manual system, you write paper

receipts. Later you update sales books.

k. It enables you to know a history of how a particular product has move in

and out within a given period.

3.8 PROCESSES IN AUTOMATION OF THE INVOICE CONTROL

SYSTEM

These steps below show the process employed by the developer in

Automation of The Inventory Control System Gamzaki Store.

1. Getting a clear understanding of the problem: - I made all enquiry

method within my reach to enquire and know the process used in the

manual process. I concentrated on the problems that are encountered

in the process involved by the manual process. Again, the various

inputs and outputs were the basic requirement were also considered

and all other conditions involved.

2. Problem Analysis: - The problem associated with the manual system

were critically observed and analyzed in detail with a hope of

providing a possible solution to them.

3. Program Design: - After analyzing the entire program should be

written as given. The program inputs and outputs are also tested. The

flow of the logic of the program is also drawn.

4. Segmenting the program: - The whole program is written in

segments so as to allow each part to be tested and debugged easily.

5. Desk Checking: - Checking of program to ensure that all syntax and

logic error are detected and corrected.

 6. Running of the program: - The program is successfully run without

and error, written and identification absolutely connection. It is

documented in case of future use reference.

3.9 SYSTEM DESIGN

The major fact taken into consideration in the design of the new system is

the automation of the inventory control system for effective management. In the

course of the design, the daily report on transactions are captured, databases

were created to keep customer order the design of computerization of invoicing

system is a creative it, which has its objective. It is a drawing or pattern

showing something is to be done. System design is also a purposeful planning.

The implementation of the system creates benefits same. Its implements

superior to those achieved by manual system, is designed according to

specification of Gamzaki Store. It is a descriptive in nature of what the system

is and what it does. This shows how the expected program is to be operated.

This project is designed to replace the old manual methods of operation

involved in calculating stocks of item.

It is designed to substitute the manual system thereby enhancing its

efficiency and accuracy. A sort of security guaranteed by the new system

designed that is more effective than that of the manual system is highly

achieved. It starts with an access method, which allows the user to go into

various area of the program; this is done by using the menu option. Thus,
 provides quick access to the different data area of the program. The design

process takes place at two levels;

3.9.1 STRUCTURE CHART

Home Page

(Main Module)

Transactions Manage Stock Settings

New Transaction Change

Transaction History Password
 Fig. 3.9.1 is the structure chart of the system design

The chart of the home page (main module) and it has three branches below:

1) Transactions: this consists of new transactions and transaction history.

2) Manage stock

3) Settings: this consists of Change Password

3.9.2 USE CASE DIAGRAM

Login
 Perform Transaction

View Transactions History

Sales Personnel Print Receipt

 Manage Stock

Change Password

Fig. 3.9.2 Diagram of the system design

1. Login: a password or code used when logging into a computer, database

or system.

2. Perform Transaction: this is the opening of a new request or order by a

customer.

3. View Transactions History: it shows the details about and payments made

by a customer.

4. Point Receipt: this is the issuing of a printed document to a customer

about a payment being made.

5. Manage Stock: This is the administrative role of assessing the inventory

of a business and making sure it is sufficient to meet consumer demand.

6. Change Password: This is the menu used by the database administrator to

change the user’s password. He alone has the right to change it.

3.10 DATA BASE DESIGN

1. Files used in this project are made up of different data types. Some of

the files are designed and linked with database. There are several
 advantages of storing data in database and MS Access database was used

in this project design.

2. All data is stored at one location when a database is used, all tables are

stored in a single file thus, and we need not deal with separate buttons

using the single database file. Though all data is stored in a single file,

distinctions exist because tables are used since each table is stored as a

separate entity in the file.

3. It is possible to define relationship between tables and these are also

stored in the database.

4. It is possible to define validation at fields as well as table level and this

ensures accuracy of data being stored.

5. Query, report, sorting etc. are also used.

3.11 DESIGN PROCESS

The design process takes place at two levels that are,

1. Logic design which is that part of the design process when you write the

detailed specification of the new system.

2. Physical design, namely the activities involved when you turn the logical

design into reality. The feature that would consider in the logical design

of “GAMZAKI INVENTORY CONTROL SYSTEM” is;

a. Data input to the system

b. Output to be produced by the system

 c. process it under goes before output is produce

d. The database structure or layout

3.11.1 INPUT SPECIFICATION

The data inputs into Gamzaki Inventory Control System are from the database

i.e sales and inventory. The input specification is shown below;

MANAGE STOCK ITEM

Table 3.11.1.1 structure of the Manage Stock table

DESCRIPTION FIELD NAMES DATA

TYPES

Serial number S/N Number

Item name StockName Text

Item Category Category Text

Cost price CostPrice Number

Selling price SellingPrice Number

Minimum Balance MinimumStockBal Number

TRANSACTION HISTORY
Table 3.11.1.2 structure of the TransactionHistory table

DESCRIPTION FIELD NAMES DATA TYPES

Serial number ID Number

Item category Category Text

Selling price Price Number

Quantity Qty Number

Total amount TotalAmount Number

Purchase date PurchaseDate Number

CHANGE PASSWORD

Table 3.11.1.3 structure of the Login Table

DESCRIPTION FIELD NAMES DATA TYPES

Serial number S/N Number

Username Username Text

Old Password Password Text

New Password Password Text

Confirm Password Password Text

3.12 OUTPUT SPECIFICATION

Specification here means arrangement of headings and details on the output

document. Whatever the medium used in both, paper document and transaction

output. The purpose is for the clarity of the output to the user.

The product sales report shows the total product sold, their unit prices and the

amounts. The entire inventory report shows the types of product in stock

without any need of counting the product of items in the shelf one after the

other in order to know the type and quantity of products in stock. It also deals

with the aspect of the unit’s prices and cost prices of goods or items in stock.

3.13 PROCESSING

There are items which are sold and distributed to customers. An order is

placed by the customer-required details which are item name and quantity. The

order processing executes, looks up the stock of each item to find out which is

available or not and then fulfills the order. After formalities are fulfilled, a bill

is generated by the system and given to the customer by printing a receipt. The

work area is automated and maintained by the management to generate a more

efficient system.
 CHAPTER FOUR

SYSTEM IMPLEMENTATION

4.1 THE IMPLEMENTATION STAGES

The implementation Stages are divided into two stages which are:

1. Programming stage

2. User training stage

4.1.1 PROGRAMMING STAGE

Visual basic.net programming language was used due to its ability to

effectively and efficiently carry out record management. In addition, to

efficiently carry out the computerized operation and to code various instructions

and to debugged it. A structural approach to programming was also called or

adopted. Each segment separately tested and the whole segment of modules

integrated to form a single program, which is the computerized inventory

system. These have the advantages of identifying and debugged error easily.

When the programmer needs a specific user interface feature such as a

button, he selects the appropriate ready to use component provided by the visual

programming environment these component can be moved, resized and

renamed as required. No need to write code to create and display commonly

required control. It provides all features that are required to develop graphical

user interface as ready to use components.

4.1.2 USER TRAINING STAGE

In this stage the developed software will be installed into the Gamzaki

Store system and then train the prospective users on how to use the new system

to perform daily sales or transaction.

4.2 SYSTEM REQUIREMENTS

The requirements for the implementation of this system are as follows;

I. Software requirement.

II. Hardware requirement.

III. Functional requirement (input/output)

IV. Non-functional requirement

4.2.1 SOFTWARE REQUIREMENTS

Software is the term used to describe all the various types of programs or

command, which enable the computer system hardware to functions or operate

effectively. Software are prepared by manufacturers of a computer system,

which are used by the computer users to perform different task, such as that of

inventory control, word processing, accounting, planning, etc the accurate

software suggested for the new system are as follows;

i. MS windows XP or Newer

ii. Visual studio (visual basic.net 2010)

iii. Microsoft Access as the database

iv. Microsoft Excel for printing sales report

4.2.2 HARDWARE REQUIREMENT

The hardware is the term used to describe all physical component of a

computer or communicating system including both mechanical and electronic

parts of the computer. The hardware required to run this automated inventory

control system is a microcomputer with the following features.

i. Processor of at least 2 GHZ clock speed

ii. 2 GB RAM

iii. Printer for printing reports

The listed configurations are the minimum requirements, but if the

configurations are of higher versions, the processing derived will definitely be

better and the program will run faster.

4.2.3 INPUT REQUIREMENTS/SPECIFICATION

The input requirement is the information or items needed that will aid the

inventory calculations or stocktaking of the items. The input specifications are:

a. Item Name

b. Selling Price

c. Quantity to be Purchase

d. Stock balance
 e. Selling Price

All the specifications above must be entered for the actual stock taking of

items.

4.2.4 OUTPUT REQUIREMENTS/SPECIFICATION

The output is the expected results from the processing which is the

transaction output. The information carries all the data pertaining to the stock

items of the such as;

a) Item name

b) Quantity

c) Price

d) Total amount

All this information will be printed out as stipulated.

4.2.5 NON- FUNCTIONAL REQUIREMENTS

I. Transaction should be completed within seconds.

II. There should be backup procedure to maintain records.

4.3 IMPLEMENTATION

The new system is designed to be put into efficient use. Here, I will look

into the various technical aspects that influenced the successful implementation

of this system and determine the effective operation of the system. System

implementation follows the approval of the system proposals and its objectives,
thus it is to arrive at a satisfactory, implemented, completed, and function

evaluated automated system.

Fig. 4.1 Welcome Form

This is the first form that appears when the software is run.

Fig 4.2 login form

This is the first form that requires the user to provide the information (i.e.

username & password) needed in order to the access the features of the

software.

Fig. 4.3 Home form

This is form seen after username and password have been supplied or inputted.

Now the features of the software can be accessed.

 Fig. 4.4 Transaction form

Transaction form is used for selling of items and issuing receipt to the customer

whenever a items are purchased

4.3.5 RECIEPT FORM

 Fig.4.5 Receipt form

This form enables the receipt of the purchased to be printed receipt and issued

to a customer.

Fig. 4.6 Manage Stock form

This interface allows the user to add new stock and update selected stock

balance.
 Fig. 4.7 Transaction History form

Transaction history is used to show the list of all sales for reference purpose.

This form is used in printing transaction record for reference purpose.

4.3.8 CHANGE PASSWORD

Fig. 4.8 change password form

Change password form allows the management or system admin to change a

password.

4.4 SYSTEM TESTING

After test running with varied data, which is after running the program,

the output was shown on the monitor. The output can also be printed on paper.

This shows that the new system was perfect and effective.

4.5 INTEGRATION

System integration is the successful putting together of the various

components, assemblies, and subsystems of a system and having them work

together to perform what the system was intended to do. After successfully

designing my Login form, Main form, Transaction History form, New

Transaction form, Manage Stock form, and Change Password form, all the

listed forms were integrated together to make up the complete system.

4.6 OPERATING THE NEW SYSTEM

This section of the project explains the job that is performed by the

program developed. First of all the various inputs listed above will be entered,

then the program processes that data and give out the required output as the

transaction output. It gives results based on what is entered as the input for this

reason all inputs must be correct and valid.

This is the detailed explanation of the operation carried out by the system

on the job that is required to do, the passing of control in the system and
 performing the task that it is required of it. All these are expected to be done

within a second, as a way to show the efficiency of the system.

Computer is required to give efficient and reliable service without the

need of intervention by the user. These requirements suggest that computer

should monitor and control its operation at all time. The operation of the system

is to enable the entire inventory control calculation or stocktaking being done

manually with greater accuracy and lesser period of time. It processes data

keyed in a remarkable moment of time far lesser than the manual process. The

central processing is that which ensures the program instructions are carried out

in the proper way of sequence and the interpretation is accordance with the

expected output.

4.7 ERROR HANDLING

i. System should report data type mismatches on fields on the form.

ii. System should report violation of authorization rights.

iii. System should report invalid login errors.

 CHAPTER FIVE

SUMMARY, CONCLUSION AND RECOMMENDATIION

5.1 SUMMARY

It can be observed that computer applications are very important in every

field of human endeavour. With this new system, the difficulties encountered

with the manual inventory control system of Gamzaki Store are overcome. The

automated inventory control system reduces the workload of the staff, saves

time and increases efficiency. The records of the company are safe and secure,

distribution process is well managed, errors are minimized, and reports

generated for management are accurate thereby increasing the profit margin. On

a general note, this project covers necessary process involved in designing any

inventory control in a retail shop. It is aimed at providing a means of helping

staff of manage sales and inventory. The approach used involves the

consultation of different individuals ranging from the owner and staff of

Gamzaki Store. The method of implementation was with the use of visual studio

2010 (visual basic.net) as the programming language, SQL as the database

engine. The basic user attention was given priority when designing the system.

Therefore, this project if embraced would address the problems of sales and

inventory management.

5.2 RECOMMENDATION
 I recommend this automated inventory control system to the Gamzaki and

any other store that still carry out their operation manually. This system will be

useful since it is computerized and will promote effective, efficient and improve

service delivery. The use of this software developed for the control of inventory

as it will make their work easier.

5.3 CONCLUSION

Anything worth doing is worth doing well. For a project of this kind, all

that was discussed and done was to the best of ability and reach.

The benefits derived from this work cannot be over emphasized as

tremendous amount of new knowledge was revealed and acquired in the course

of study for this project work.

 REFERENCES

Buffa E, Salin R(1987) . Moredern Productions and Operations management, 8 th

Ed. New York: John Wiley and Sons

Byoungho, J., (2004) “Achieving an Optimal Global Versus Domestic Sourcing

Balance under Demand Uncertainty”. International Journal of Operations and

Production Management. Bradford. Vol.24, Iss 11/12, p.1292

Dimitrios P. Koumanakos, (2008) “The effect of inventory management on

Firm Performance”, International Journal of productivity and Performance

management, Vol. 57 Iss: 5, pp. 355-369.

Ellram, Lisa M. (1996), “The Use of the Case Study Method in Logistics

Research,” Journal of Business Logistics. Vol. 17, No. 2, pp. 93-139.

Evangelos Petroutsos ,(2002). Mastering Visual Basic.NET. SYBEX Inc.

Graman, G.A. and Magazine, M.J., (2006) “Implementation issues influencing

the decision to adopt postponement” International Journal of Operations &

Production Management;Volume: 26 Issue: 10; pg.

Handfield, R.B. (2002), "Reducing costs across the supply chain", Optimize,

Dec., pp. 54-60.

Khan S., (2003) “Supplier choice criteria of executing agencies in developing

countries.”The International Journal of Public Sector Management; 16, 4/5;

ABI/INFORM Global, pg. 261

Langabeer, J., Stoughton, T., (2001) “Demand planning and forecasting in the

high technology industry. The Journal of Business Forecasting Methods &

Systems. Flushing: Vol.20, Iss. 1; pg. 7, 4 pgs

Lyson K (1996). Purchasing and Chattered Institute of Purchasing and Supply,

London: Pitman Publishing.

Monczka, R.M, Trent, RJ. andHandfield, R.B. (2002), Purchasing and Supply

Chain Management,2nd éd., South-Western, Cincinnati, OH. National Science

Foundation Science Engineering Indicators -1998N

Nyabwanga, R.N & Ojera, P.(2012). Inventory management practices and

business performance for small scale enterprises in Kenya. Journaal of business

management, 4.

Rajeev, N. (2008) an evaluation of inventory management in Indian machine

tool SME:An eeploratory. 4th IEEE international conference on management of

innovation and technology(pp. 1412-1417)

Salawati, S., Tinggi M. & kadri, N.(2012) Inventory Management in

Malaysian construction Firms: impact on performance. SIU Journal

Management, 2, 59-60. (Rajeev, 2008)

Wallin, C., Rungtusanatham, M.J., and Rabinovich, E., (2006) “What is the

"right" inventory management approach for a purchased item?” International

Journal of Operations & Production Management. Bradford: Vol. 26, Iss. 1/2;

pg. 50, 19 pgs

Ying Bai, (2012). Practical Database Programming with VisualBasic.NET. (2 nd

Edition), IEEE Press, John Wiley & Sons, Inc., Publication.

APPENDIX

SOURCE CODE

MODULE 1:

Module Module1

Public con As New OleDb.OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0; data

source=" & Application.StartupPath & "/Dbase.accdb")

End Module

SPLASH SCREEN:
Public Class splashScreen

Private Sub Timer1_Tick(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Timer1.Tick

ProgressBar1.Value = ProgressBar1.Value + 1

If ProgressBar1.Value = 90 Then

ProgressBar1.Enabled = False

Timer1.Enabled = False

Me.Hide()

loginFrm.Show()

End If

End Sub

Private Sub ProgressBar1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles ProgressBar1.Click

End Sub

End Class

LOGIN FORM:

Public Class loginFrm

Private Sub loginBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles loginBtn.Click

con.Open()

Dim cmd As New OleDb.OleDbCommand("SELECT * FROM LoginTable WHERE username='"

& Me.usernameTxtbox.Text & "' AND password='" & Me.passwordTxtbox.Text & "'", con)

Dim dr As OleDb.OleDbDataReader : dr = cmd.ExecuteReader

If dr.Read = True Then

homeFrm.Show()

Me.Hide()

Else
 MsgBox("Invalid username or password", MsgBoxStyle.Critical)

usernameTxtbox.Text = ""

passwordTxtbox.Text = ""

End If

con.Close()

End Sub

Private Sub cancelBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cancelBtn.Click

End

End Sub

Private Sub cancelBtn_MouseHover(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles loginBtn.MouseHover, cancelBtn.MouseHover

CType(sender, Button).BackColor = Color.Navy

End Sub

Private Sub loginBtn_MouseLeave(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles loginBtn.MouseLeave, cancelBtn.MouseLeave

CType(sender, Button).BackColor = Color.Lavender

End Sub

End Class

HOME FORM:

Public Class homeFrm

Private Sub ManageStockToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs)

manageStock.Show()

End Sub
 Private Sub NewTransactionToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles NewTransactionToolStripMenuItem.Click

transactionFrm.show()

End Sub

Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles ExitToolStripMenuItem.Click

End

End Sub

Private Sub ChangePasswordToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles ChangePasswordToolStripMenuItem.Click

loginSetFrm.Show()

End Sub

Private Sub InventoryToolStripMenuItem_Click(ByVal sender As System.Object, ByVal

e As System.EventArgs) Handles InventoryToolStripMenuItem.Click

manageStock.Show()

End Sub

Private Sub TransactionHistoryToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

TransactionHistoryToolStripMenuItem.Click

transacHisFrm.Show()

End Sub

Private Sub MenuStrip1_MouseHover(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MenuStrip1.MouseHover

CType(sender, MenuStrip).BackColor = Color.Navy

End Sub
 Private Sub MenuStrip1_MouseLeave(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MenuStrip1.MouseLeave

CType(sender, MenuStrip).BackColor = Color.Lavender

End Sub

End Class

TRANSACTION FORM:

Public Class homeFrm

Private Sub ManageStockToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs)

manageStock.Show()

End Sub

Private Sub NewTransactionToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles NewTransactionToolStripMenuItem.Click

transactionFrm.show()

End Sub

Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles ExitToolStripMenuItem.Click

End

End Sub

Private Sub ChangePasswordToolStripMenuItem_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles ChangePasswordToolStripMenuItem.Click

loginSetFrm.Show()

End Sub

Private Sub InventoryToolStripMenuItem_Click(ByVal sender As System.Object, ByVal

e As System.EventArgs) Handles InventoryToolStripMenuItem.Click

 manageStock.Show()

End Sub

Private Sub TransactionHistoryToolStripMenuItem_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

TransactionHistoryToolStripMenuItem.Click

transacHisFrm.Show()

End Sub

Private Sub MenuStrip1_MouseHover(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MenuStrip1.MouseHover

CType(sender, MenuStrip).BackColor = Color.Navy

End Sub

Private Sub MenuStrip1_MouseLeave(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MenuStrip1.MouseLeave

CType(sender, MenuStrip).BackColor = Color.Lavender

End Sub

End Class

RECEIPT FORM:

Public Class receipt

Private Sub receipt_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

dateLbl.Text = Today

For i = 0 To transactionFrm.DataGridView1.RowCount - 2

With DataGridView1

.Rows.Add()
 .Rows(i).Cells(0).Value = i + 1

.Rows(i).Cells(1).Value =

transactionFrm.DataGridView1.Rows(i).Cells(1).Value

.Rows(i).Cells(2).Value =

transactionFrm.DataGridView1.Rows(i).Cells(2).Value

.Rows(i).Cells(3).Value =

transactionFrm.DataGridView1.Rows(i).Cells(3).Value

.Rows(i).Cells(4).Value =

transactionFrm.DataGridView1.Rows(i).Cells(4).Value

End With

Next

totalLbl.Text = transactionFrm.totalTxtBox.Text

End Sub

Private Sub printBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles printBtn.Click

printBtn.Visible = False

PrintForm1.PrintAction = Printing.PrintAction.PrintToPreview

PrintForm1.PrintAction = Printing.PrintAction.PrintToPrinter

PrintForm1.Print()

printBtn.Visible = True

Me.Close()

End Sub

End Class

TRANSACTION HISTORY FORM:

Imports Microsoft.Office.Interop.Excel

Public Class transacHisFrm

 Private Sub transacHisFrm_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

con.Open()

Dim da As New OleDb.OleDbDataAdapter("SELECT Item, Category, Price, Qty,

TotalAmount, PurchaseDate FROM TransactionHistory", con)

Dim dt As New System.Data.DataTable

da.Fill(dt)

Me.DataGridView1.DataSource = dt

con.Close()

End Sub

Private Sub printBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles printBtn.Click

With Me.DataGridView1

If ((.Columns.Count = 0) OrElse (.Rows.Count = 0)) Then

Exit Sub

End If

Dim dset As New DataSet

dset.Tables.Add()

For g = 0 To .ColumnCount - 1

dset.Tables(0).Columns.Add(.Columns(g).HeaderText)

Next

Dim dr As DataRow

For g = 0 To .RowCount - 1

dr = dset.Tables(0).NewRow

For j = 0 To .Columns.Count - 1
 dr(j) = .Rows(g).Cells(j).Value

Next

dset.Tables(0).Rows.Add(dr)

Next

Dim excel As New Microsoft.Office.Interop.Excel.Application

Dim wBook As Microsoft.Office.Interop.Excel.Workbook

Dim wsheet As Microsoft.Office.Interop.Excel.Worksheet

wBook = excel.Workbooks.Add

wsheet = wBook.ActiveSheet

Dim dt As System.Data.DataTable = dset.Tables(0)

Dim dc As System.Data.DataColumn

Dim dr1 As System.Data.DataRow

Dim colindex As Integer = 0

Dim rowindex As Integer = 0

For Each dc In dt.Columns

colindex = colindex + 1

excel.Cells(1, colindex) = dc.ColumnName

Next

For Each dr1 In dt.Rows

rowindex = rowindex + 1

colindex = 0

For Each dc In dt.Columns

colindex = colindex + 1

excel.Cells(rowindex + 1, colindex) = dr1(dc.ColumnName)

Next

Next
 wsheet.Columns.AutoFit()

Me.FolderBrowserDialog1.ShowDialog()

Dim fname As String = Me.FolderBrowserDialog1.SelectedPath & "\

Transaction" & DateString

Dim blnFileOpen As Boolean = False

Try

Dim FTemp As System.IO.FileStream = System.IO.File.OpenWrite(fname)

FTemp.Close()

Catch ex As Exception

blnFileOpen = False

End Try

If System.IO.File.Exists(fname) Then

System.IO.File.Delete(fname)

End If

MsgBox("Transaction Report Has been Exported Successfully!",

MsgBoxStyle.Information, "Confirmation!")

wBook.SaveAs(fname)

excel.Workbooks.Open(fname)

excel.Visible = True

End With

End Sub

Private Sub backBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles exitBtn.Click

Me.Close()

End Sub
End Class

MANAGE STOCK FORM:

Public Class manageStock

Private Sub searchBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles searchBtn.Click

If nameTxtbox.Text = "" Then

MsgBox("Please Enter a Valid Stock Name", MsgBoxStyle.Exclamation +

MsgBoxStyle.OkOnly)

Else

con.Open()

Dim cmd As New OleDb.OleDbCommand("SELECT * FROM ManageStock WHERE

StockName = '" & nameTxtbox.Text & "'", con)

Dim dr As OleDb.OleDbDataReader : dr = cmd.ExecuteReader

If dr.Read = True Then

Me.categoryCmb.Text = dr("Category").ToString

Me.balTxtbox.Text = dr("StockBalance").ToString

Me.cpTxtbox.Text = dr("CostPrice").ToString

Me.spTxtbox.Text = dr("SellingPrice").ToString

Me.minbalTxtbox.Text = dr("MinimumStockBal")

End If

con.Close()

End If

End Sub

Private Sub addBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles addBtn.Click

con.Open()
 If nameTxtbox.Text <> "" And categoryCmb.Text <> "" And balTxtbox.Text <> ""

And cpTxtbox.Text <> "" And spTxtbox.Text <> "" And minbalTxtbox.Text <> "" Then

Dim cmd As New OleDb.OleDbCommand("INSERT INTO ManageStock (StockName,

Category, StockBalance, CostPrice, SellingPrice, MinimumStockBal) VALUES ('" &

nameTxtbox.Text & "','" & categoryCmb.Text & "','" & balTxtbox.Text & "','" &

cpTxtbox.Text & "','" & spTxtbox.Text & "','" & minbalTxtbox.Text & "')", con)

Dim dr As OleDb.OleDbDataReader : dr = cmd.ExecuteReader

MsgBox("Stock Added", MsgBoxStyle.Information + MsgBoxStyle.OkOnly)

Dim da As New OleDb.OleDbDataAdapter("SELECT * FROM ManageStock", con)

Dim dt As New DataTable

da.Fill(dt)

Me.DataGridView1.DataSource = dt

nameTxtbox.Text = ""

categoryCmb.Text = ""

balTxtbox.Text = ""

cpTxtbox.Text = ""

spTxtbox.Text = ""

minbalTxtbox.Text = ""

Else

MsgBox("Please Fill Empty Fields", MsgBoxStyle.Exclamation +

MsgBoxStyle.OkOnly)

End If

con.Close()

End Sub

Private Sub updateBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles updateBtn.Click

con.Open()
 Dim cmd As New OleDb.OleDbCommand("SELECT * FROM ManageStock WHERE StockName =

'" & Me.nameTxtbox.Text & "'", con)

Dim dr As OleDb.OleDbDataReader : dr = cmd.ExecuteReader

If dr.Read = True Then

Dim cmdUpdate As New OleDb.OleDbCommand("UPDATE ManageStock SET

StockBalance = '" & balTxtbox.Text & "', CostPrice = '" & cpTxtbox.Text & "',

SellingPrice = '" & spTxtbox.Text & "' WHERE StockName = '" & nameTxtbox.Text & "'",

con)

cmdUpdate.ExecuteNonQuery()

cmdUpdate.Dispose()

End If

Dim da As New OleDb.OleDbDataAdapter("SELECT * FROM ManageStock", con)

Dim dt As New DataTable

da.Fill(dt)

Me.DataGridView1.DataSource = dt

MsgBox("Record Updated", MsgBoxStyle.Information + MsgBoxStyle.OkOnly)

con.Close()

End Sub

Private Sub closeBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles exitBtn.Click

Me.Close()

End Sub

Private Sub manageStock_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

con.Open()

Dim da As New OleDb.OleDbDataAdapter("SELECT * FROM ManageStock", con)

 Dim dt As New DataTable

da.Fill(dt)

Me.DataGridView1.DataSource = dt

con.Close()

End Sub

Private Sub backBtn_MouseHover(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles updateBtn.MouseHover, exitBtn.MouseHover, addBtn.MouseHover

CType(sender, Button).BackColor = Color.Navy

End Sub

Private Sub backBtn_MouseLeave(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles updateBtn.MouseLeave, exitBtn.MouseLeave, addBtn.MouseLeave

CType(sender, Button).BackColor = Color.Lavender

End Sub

Private Sub searchBtn_MouseHover(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles searchBtn.MouseHover

searchBtn.BackColor = Color.Navy

End Sub

Private Sub searchBtn_MouseLeave(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles searchBtn.MouseLeave

searchBtn.BackColor = Color.Lavender

End Sub

End Class

CHANGE PASSWORD FORM:

Public Class loginSetFrm

 Private Sub okBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles okBtn.Click

con.Open()

Dim cmd As New OleDb.OleDbCommand("SELECT * FROM LoginTable WHERE username =

'" & Me.unameTxtbox.Text & "' And password = '" & Me.opTxtbox.Text & "'", con)

Dim dr As OleDb.OleDbDataReader : dr = cmd.ExecuteReader

If dr.Read = True Then

Dim cmdUpdate As New OleDb.OleDbCommand("UPDATE LoginTable SET [password]

='" & npTxtbox.Text & "' WHERE username ='" & Me.unameTxtbox.Text & "'", con)

cmdUpdate.ExecuteNonQuery()

cmdUpdate.Dispose()

MsgBox("Password Changed", MsgBoxStyle.Information + MsgBoxStyle.OkOnly)

Else

MsgBox("Invalid username or password", MsgBoxStyle.Critical)

End If

con.Close()

End Sub

Private Sub cancelBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles cancelBtn.Click

unameTxtbox.Text = ""

opTxtbox.Text = ""

npTxtbox.Text = ""

cnpTxtbox.Text = ""

End Sub

Private Sub exitBtn_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles exitBtn.Click

Me.Close()

End Sub

End Class