CHAPTER ONE

INTRODUCTION

1.00 BACKGROUND OF THE STUDY

Electronic Data Interchange (EDI) is commonly defined as the direct

computer-to-computer exchange of standard business firms. It clearly requires

a business process, because the key idea involved is the exchange of

document that allows a business application to take place without human

intervention. Data processing is clearly necessary for application processing,

Data communication is then necessary for the exchange to take place. It is the

marrying of these three disciplines (business, data processing and data

communication) that allow the “paperless trading” that comprises EDI

technologies.

Electronic Data Interchange (EDI) is simply a set of data definitions that

permit business forms that would have been exchanged using paper in the

past, to be exchanged electronically. This simple set of definition has spurred a

number of organizations to put in place an operational environment in which the

exchange of electronic business forms substitute for the exchange of paper

forms. This has resulted in some cases, in the establishment of an EDI

environment, which arguably represents the most advanced state of electronic

commerce (EC) today causing some to view EDI and EC as one and the same.

We see EDI only as a subset of EC. As such EDI provides an excellent

example of a working electronic commerce environment and is a good starting

point for examining Electronic Commerce (EC).

1
1.01 STATEMENT OF THE PROBLEM

This project is built to effectively handle business transitions online, apart

from adding basic functions to navigate through the application, we will also add

features that enable a client/customer to efficiently view the prices of each

product online, purchase product online by filling a transaction form and should

be able to send a report to the client or customer.

This project (EDI) will also serve as a resource, a guide and an advocate

for the owner (company or organization).

1.02 PURPOSE OF THE STUDY

There is no doubt that for a project to be effective, there must be objective

to achieve an efficient result. This project is therefore aimed at designing and

implementing an Electronic Data Interchange Interface for a business platform

that can transact business electrically avoiding the need to either physically

take the document from one office to another or keying in data again and again

involving the attendant problems of manual labour and errors creeping in at

each stage of data entry.

1.03 SIGNIFICANCE OF THE STUDY

The significance of this project is to design a business oriented interface

to serve as a mediator between customer/client and the database.

1.04 SCOPE OF THE STUDY

The research is study under the confinement work of Electronic

Commerce (EC) as a whole. In pursuance of the objective of the study;

attention shall be focused on Electronic Data Interchange (EDI) among other

2
electronic commerce implementation. In order to conduct am empirical

investigation into the adoption of Electronic Data Interchange in business

organizations and firms, and also to examine the nature of EDI operations in

the business world. The scope of this research covers from the existence or

history of E-Commerce to date.

1.05 LIMITATION OF THE STUDY

This project work is only concerned with the design and implementation of

an Electronic Data Interchange interface for a business application. During the

course of this project I was constraint and faced with some problems such as:

(a) Acquisition of information:- The information needed to enhance this work

is not available on hardcopy and those on the internet are not structured. Due

to this constraint there was difficulty in designing a system to match the existing

method. The installation/downloading of EDI framework were not easy.

(b) Financial constraint:- The cost of achieving an efficient Electronic Data

Interchange online is very high and also to get visual basic. Net programming

language software to design the interface was not available, so I used visual

basic 6.0 as substitute.

(c) Lack of the technical know-how on the administrator who will use the

system is another major problem.

1.06 DEFINITION OF TERMS

ELECTRONIC: Device having components such as microchips and translators

that control and direct current.

DATA: These are raw facts needed to process information.

3
INTERCHANGE: This is the exchange of information or data between two

entities.

INTERFACE: A program where two things meet and interact, e.g enabling a

user to communicate with a computer.

TRANSACTION: This is an exchange between two or more entities for the

purpose of conducting business.

DESIGN: This is a plan or drawing produced to show the look and function of

something before it is built or made.

SYSTEM: A device with several different interacting parts.

SOFTWARE: This a program and other operating information used by a

computer.

BUSINESS: This is concerned with commercial activity or a commercial

organization.

EDI: Electronic Data Interchange Interface is a direct computer-to-computer

exchange of standard business firm.

4
 CHAPTER TWO

LITERATURE REVIEW

2.00 HISTORY OF ELECTRONIC DATA INTERCHANGE (EDI)

Electronic data interchange is the transmission, in a standard syntax, of

information, business significance between computers of independent

organizations. EDI is the common “language” used to get information from one

computer system to another. It is one of the tools that makes electronic

commerce possible and delivers the cost savings businesses seek. Electronic

data interchange has traditionally been concerned with products and services

that have a short shelf life but a high unit cost. Early adopters of the use of

electronic means to replace paper transactions can be located in the

distribution and transportation industries such as the airlines, trucking, railroads,

and in the automotive industry as early as 1960. Standards development for

electronic data interchange has been traced back to the 1970s. In 1975, there

were 45 transactions sets established for the transportation industry. Today, the

ANSI (American National Standards Institute), ASC (Accredited Standard

Committee) X.12 has over 200 transaction sets associated with it covering a

wide variety of industries and businesses. By the mid 1980s, two general

purpose industry standards in electronic data interchange had emerged. In

1986, the United Nations Electronic Data Interchange for Administration,

Commerce and Transport (EDIFACT) took shape while the ANSI X.12 in the

United States continued to expand. These two standards have benefited

business by prescribing ways of structuring data according to agreed message

5
standards between independent computer systems. Structuring the data allows

for the presentation of the content of a document to be interpreted without error

and for the data to be acted upon using automatic processing which reduces

the need for human intervention in the process. Traditionally, it has been the

larger companies who had the investment dollars to fund development of

electronic data interchange activity for themselves and many times for their

suppliers or trading partners. Use of EDI has grown. The reduction of costs of

computing hardware, software, and telecommunications combined with trade

agreements negotiated globally have brought EDI to the attention of business of

all sizes as a desirable and necessary method of conducting commerce. Today

the use of electronic data interchange extends to all trade and trade related

activities. Banking and finance, healthcare industries, manufacturing, retail,

tourism and travel, transport industries of all types, and governmental

enterprise all use electronic data interchange to conduct business. It is

estimated that there are tens of thousands of EDI users in North America as

well as many users in the Pacific Rim and Europe. Because of the varied

implementations across types of commerce varied approaches and definitions

of EDI have developed.

“Electronic data interchange is the transmission, in a standard syntax of

unambiguous information of business or strategic significance between

computers of independent organizations”. The Accredited standards committee

for EDI of the American National Standards Institute.

6
“Electronic data interchange is the interchange of standard formatted data

between computer application systems of trading partners with minimal manual

intervention”. UN/EDIFACT Training Guide.

“Electronic data interchange is the electronic transfer, from computer to

computer to another of computer process able data using an agreed standard

to structure the data”. International Data Exchange Association, the EDI

Handbook: Trading in the 1990s.

Although the definitions vary, four components of EDI remain the same.

EDI can be characterized as having a component that works with application

level service such as purchasing or inventory of the data, EDI uses some

method of transporting the data or messages such as electronic message or

world wide web tools, and EDI uses a communication method such as the

Internet of dial up lines to move the data from one computer to another

computer.

BENEFITS OF EDI OVER THE PAPER SYSTEM

The benefits of a properly implemented, fully integrated EDI system can

be seen throughout the operations of the business and its trading partner

community in a number of ways.

Increase speed: Business documents are exchanged electronically rather than

physically. Computer-to computer communication means that transactions can

be completed in a matter of minutes, rather than days. Consequently, the

activities that are initiated by these transactions can begin to occur immediately.

Some examples are:

7
 Receipt of the order is acknowledged automatically

 Order processing can begin immediately without the need to be manually

entered into the seller’s system.

 When the order is complete, shipment can be arranged and

communicated electronically.

Improved accuracy: Information that is exchange electronically does not

require manual transcription/data entry thus, decreasing the potential sources

of error caused by re-entry of data and handling paper involved in order. This

effectively eliminates the introduction of errors into the initial business process

or other business systems that may be affected by further downstream.

Cost savings/Error avoidance: As organizations shift from manual to

electronic processes using EDI, they will realize significant cost savings. Some

of these savings are a direct result of increased speed. For example correcting

errors cost an organization both time and money; so the reduction of errors

also reduces cost.

Improved cash flow: As more of a company’s applications are integrated into

EDI, its cash flow will improve due to overall efficiencies that EDI provides. For

Example, invoices can be processed more quickly, allowing sellers to receive

and apply payments more quickly.

Reduced overhead costs: Reducing postage bills and manual processing

costs involved with paper filing systems, costs for paper, envelopes, and

8
mailing materials decrease as well as those for telephone and courier services

used to support transmission of orders and paper documents.

Better planning and processing: In an electronic environment, rapid receipt

of accurate and complete business transactions is the norm. Suppliers can

process orders more quickly and shipments can be scheduled accordingly.

Increased transaction visibility: Paper documents are replaced with

electronic transactions, it is easy to maintain electronic logs or audit trials of

document handling activity. This provides the ability to track status and

measure performance throughout the entire process. Improved customer

service levels: As business is handled more quickly and accurately, EDI

enhances the image of the company and increase the company ability to

provide faster and better customer service. (Kumar, Ram and Connie W.C

(1996).

BARRIERS TO THE IMPLEMENTATION OF EDI

There are a few barriers to adopting electronic data interchange.

 One of the most significant barriers is the accompanying business

process change. Existing business processes built around slow paper handling

may not be suited for EDI and would require changes to accommodate

automated processing of business documents.

 Another significant barrier is the cost in time and money in the initial set-

up. The preliminary expenses and time that arise from the implementation,

customization and training can be costly and therefore may discourage some

businesses.
9
 The Key hindrance to a successful implementation of EDI is the

perception many businesses have of the nature of EDI. Many view EDI from

the technical perspective that EDI is a data format; it would be more accurate

to take the business view that EDI is a system for exchanging business

documents with external entities.

2.01 ELECTRONIC COMMERCE (EC)

Electronic commerce is a broad term which generally describes business

activities which are conducted electronically. Within the boundaries of

electronic commerce, large bodies of information can be found concerning

global information, reengineering workflows, marketing strategies to enhance

competiveness, electronic data interchange, electronic funds transfer and other

payment systems, network security, value added networks, and the Internet.

This project is intended to focus on Electronic Data Interchange and will also

discus Value Added Networks (VANs), network security issues, and the

Internet as a new vehicle for electronic commerce activity.

2.02 E-BUSINESS (ELECTRONIC BUSINESS)

E-business derived from such terms as “e-mail” and “e-commerce”, is the

conduct of business on the internet, not only buying and selling but also

servicing customers and collaborating with business partners. One of the first

to use the term was IBM, in October 1977; it launched a thematic campaign

built around the terms of the internet and its new culture and capabilities.

Companies are using the web to buy parts and supplies from other companies,

to collaborate on sales promotions, and to do joint research. Exploiting the

10
convenience, availability and world-wide reach of the internet, many

companies such as Amozon.com the book sellers have already discovered

how to use the internet successfully.

IMB considers the development of intranets and extranets to be part of e-

business, this can be said to include e-service, the provision of service and

task over the internet by application service providers (ASP).

2.03 DIRECT EDI OR POINT-TO-POINT EDI

Direct EDI as this implies, is a direct link between two computers. Direct

EDI typically requires considerable expertise to incorporate EDI translation

software into an organization’s computing environment but it is also

considerably cheaper than other methods and as such is often preferred to

support high-volume ordering. Rogue data provides a unique, secure point-to-

point capability over the internet.

Direct connection EDI requires each business in the network to operate

and own its site EDI translator computer. These EDI translator computers are

then connected directly to each other using modems and dial-up telephone

lines or dedicated leased lines. The dial-up option becomes troublesome when

customers or vendors are located in different time zones and transaction are

time-sensitive over high in volume. The dedicated leased line option can

become very expensive for business that must maintain many connections

with customers or vendors. Trading partners that use different communication

protocols can make both direct connection option different to implement. Below

is the diagram shown in figure 2.1

11
 Warehouse Bank Motor freight Air freight
carrier carrier

Spare parts
manufacture
r

Retailer Distributor Wholesaler Finished goods

manufacture

Fig 2.1 Direct connected EDI

2.04 VALUE ADDED NETWORKS (VAN) INDIRECT EDI

There are a number of ways EDI messages are transmitted between

trading partners. The most common method is the use of a value added

network or VAN. The requirement to communicate with trading partners, their

banks, distributors, suppliers, and everyone involved in the trade cycle gave

rise to the idea of creating networks of service providers that would offer a

single channel for facilitating all aspects of this communication. When a

company joins a VAN, it places its focus on its hardware equipment and the

links it needs to put into place to connect to the VAN, letting the VAN to be

concerned with all of the other links to the other ends and all of the issues in

between. It is cost effective for all to use the same VAN. If your trading

partners belonged to a VAN different from yours, you had no choice but to

12
belong to more than one VAN. The diagram below shows an indirect

connection of EDI through a value added network in figure 2.2

Motor freight
carrier Air freight
Bank carrier

Warehouse Spare parts

VAN manufacturer

Retailer
Finished goods
manufacture
Distributor Wholesaler

Fig 2.2 Indirect connected EDI through a VAN

Additional services are provided by VANs as well. They include mail boxing

which is the equipment of the electronic post office box. Security is provided to

protect the sensitivity of your business order and trade relationships. Various

password schemes and acknowledgement schemes are used. Checking is

also done along the way to halt incomplete transmissions or faulty

transmission. Through a VAN trading patterns you can make certificate

replacement much easier (Canis, 1995).

Some advantages of VAN

 Value Added Networks are the go-between in EDI communications.

 The VAN is responsible for routing, storing and delivering EDI messages.

They also provide delivery reports.

13
 Depending on the VAN type, messages may need extra envelopes or

may be routed using intelligent VANs which are able to read the EDI

message itself.

 VANs may be operated by various entities:

o Telecom companies;

o Industry group consortia;

o A large company interacting with its suppliers/vendors.

2.05 EDI ON THE INTERNET

As the internet gained prominence as a tool for conducting business,

trading partners who had been using EDI began to view, the internet as a

potential replacement for the expensive leased lines and dial-up connection

they had been using to support both direct and VAN added EDI. Companies

that had been unable to afford EDI began to look at the internet as an enabling

technology that might get them back in the game of selling to large customers

who demand EDI capabilities of their suppliers.

The major road blocks to conducting EDI over internet initially were

general concerned with security and the internet’s general inability to provide

audit logs and third-party verification of message transmission and delivery.

The lack of the third party verification continues to be an issue, since the

internet has no in-built facility for that. EDI transactions are business contracts

and often involved large amount of money. The issue of non-repudiation is

14
significant. The non repudiation function was provided either by a VAN’S audit

logs for indirect connection EDI or a comparison of the reading partner’s

message logs for direct connection EDI.

2.06 EDI Standards

The standards are necessary part of EDI in every standard business

application files that are used to manipulate their data in ways that are familiar

to the business. The EDI standard says which pieces of information are

mandatory for a particular document, which pieces are optional and giver rules

for the structure of the document, two EDI documents can follow the same

standard and contain different sets of information. For example a food

company may indicate a product’s expiration date while a clothing

manufacturer would choose to send colour and size information (Kimberly

1991).

The problem is that most businesses, though using the same types of

data, do not use the same application programs or hardware and software

platforms. If businesses are to be able to communicate their data to one

another, they must have a common ground to meet and to allow the exchange

of the information. Standards are the solutions to this problem. All business

that conforms to specific standards can share data in the formats delineated by

those standards. There are some major sets of EDI standards:

 The UD standard ANSI ASC X 12 (X12) is predominant in North

America.
15
  The TRADACOMS standard development by the ANA (Article

Numbering Association) is predominant in the UK retail industry.

 The ODETTE standard used within the European automotive industry.

All of these standards first appeared in the early to mid 1980s. The

electronic document interchange for administration, commerce and transport

(EDIFACT) is the UN (United Nation) standards that the whole has agreed to

eventually adopt. These early industry-specific of data interchange efforts were

very helpful; their benefits were limited to members of the industries that

created standard setting groups. From that exchange data in a standard

formats are said to be EDI – compatible, the full realization of electronic data

interchange’s economic and efficiencies required standards that could be used

by companies in all industries.

2.07 EDI SECURITY ISSUES

As the basic Transfer control protocol/internet protocol (TCP/IP) structure

of the internet was enhanced with secured protocols such as HTTP and

various encryption schemes, business worried less about security issues

although concerns still existed.

Security is clearly a difficult problem area and many products have

produced which offer various methods of control. Some of the methods use to

ensure access control and authentications are password protection, encrypted

smart cards, biometrics, and firewalls etc. Security issues are grouped into four

basic categories of concern:

16
 Privacy concerns
 Access control concerns
 Concerns about integrity and authentication.
Security issues seem to be the paramount concern with “EDU”, the value

added network service provider has been able to serve as the security enforcer

in the cycle using a closed circuit limited, circle of subscribers who pay the

price for the added value. New security techniques which give businesses the

confidence they need concerning the security needed for their electronic

commerce transactions. Data and transactions security is needed to ensure

that the privacy and confidentiality as well as authenticity of the messages are

good. Without strong security in place, EDI would not move forward. (Cavalli,

Dr. Alexander, 1995) The security modules are as shown below in figure 3.

Application Translation Translation Application

program software software program

X12 X12
File File

Security Security
software software

Verify
Apply

Signature
Authenticatio
n Apply
Apply
Encryption
Apply
Authentication
17
Encryption
 Authenticatio
Signature
n
Fig. CONFIDENTIALITY
2.08 3 security modules

Confidentiality requires that all communication between parties is

restricted to the parties involved in the transaction. This confidentiality is an

essential component in user privacy, as well as in protection of proprietary

information services. Confidentiality is concerned with the unauthorized

viewing of confidential or proprietary data that one or both of the trading

partners do not know others by confidentiality it is provided by encryption.

Encryption: Is the scrambling of data so that it is indecipherable to anyone

except the intended recipient. Encryption prevents snoopers, hackers and

other preying eyes from viewing data that are transmitted over

telecommunication channels. There are two basic encryption schemes,

private-key and public-key encryption.

 Private-key encryption: requires that both sending and receiving parties

have the same private-encryption keys. The sender encrypts the data using

his key. The receiver then decrypts the message using his identical key. There

are several disadvantages to private-key encryption. In order to remain

secured, the keys must be changed periodically and the users must be in

synch as to the actual keys being used.

 Public-key encryption: is gaining wide spread acceptance as the

preferred encryption technology. With public-key encryption, a message

18
recipient generates a matched set of keys, one public key and one private

key. The recipient broadcasts the public key to all senders or to a public

location where the key can be easily retrieved. The message users who need

to send the receiver an encrypted message use the recipient’s key to encrypt

the message. The private key, which is held in private by the recipient, is the

key that can decrypt messages encrypted with the matched public key.

One of the positive features of this method is that only one key needs to

be managed because only one key is secret; the security concerns for privacy,

access control, authentication, and integrity of the files or messages still

remain in place. Methods of encryption used with email include privacy

enhanced ail (PEM) encryption in general is cumbersome and expensive.

Authentication: Both parties should feel comfortable that they are

communicating with the party with whom they think they are doing business. A

normal means of providing authentication is through the use of passwords or

digital certificates that function like ID cards.

Data integrity: Data sent as part of a transaction should not be modifiable in

transit. Similarly it should not be possible to modify data in storage. Data

integrity is a guarantee that what was sent by the sender is actually what is

received by the receiver. This is necessary if there is a need to ensure that the

data have not been changed either inadvertently or maliciously. However,

providing data integrity is cumbersome and not used unless one of the trading

partners requires it. The normal mechanism for acquiring data integrity is for

19
the sender to run algorithms against the data that is being transmitted and

transmit the result of the algorithm separately from the transmission. Upon

receipt of the transmission, the receiver runs the identical algorithm and then

compares the results. If the results are identical, then the data have not been

modified.

Non-repudiation: Neither party should be able to deny having participated in

a transaction after the fact. The current technology ensures this through the

use of digital signatures.

The financial benefits which accrue from using these methods are

substantial. Many companies have pioneered and perfected the use of

electronic data interchange methods on their mainframe computers because

of these securities.

20
 CHAPTER THREE

SYSTEM ANALYSIS AND DESIGN

3.00 SYSTEM ANALYSIS

Systems are designed to solve problems. We can think of the system

approach as an organized way of dealing with a problem.

System analysis and design mainly encompass the processes or steps involve

in software development. In this project, i simply refer to system analysis as the

process of analyzing the existing system in terms of its problems, working

methods and detailed description of the system.

For the purpose of designing a new system the analysis steps often

require looking at the current and proposed system and refining the estimates

of benefits and cost. Data gathering and sources of information were both on

primary and secondary methods of data collection; proper data scrutiny was

done so as to be able to implement this project work more effectively.

3.01 FUNCTIONAL REQUIREMENT

The main functional requirement of this project work-“Electronic Data

Interchange” (EDI) for business is to design an interface application or software

as the case maybe to handle business transaction thereby interchanging

business document like order list, customer detail list, receipt etc. between two

or more companies without the intervention of a sales representative. This

21
software will act as an advocate for the owner of the business. In this project,

software will be developed to perform the functional requirement above.

3.02 DESCRIPTION OF THE EXISTING SYSTEM

Before the advent of EDI, there was a way of interchanging business

document between two or more businesses or individual and this method is

what we referred to as existing system in this project work.

The process of using a person or a computer to generate a paper having

another person enter the data into a trading partner’s computer was slow,

inefficient, expensive, redundant and unreliable. Due to these short comings a

better and more suitable method of interchanging data electronically was

realized which is known as Electronic Data Interchange.

3.03 DESCRIPTION OF THE PROPOSED SYSTEM

The proposed system is a business oriented interface that can

interchange like receipt order list, customer detailed list, etc. between two

persons that is the producer and the customer or the seller and the buyer.

Therefore, the proposed system in this project work is a software that

interchanges business documents.

3.3.1 ARCHITECTURE OF THE PROPOSED SYSTEM

This represents the logical and the physical arrangement of the

component that will make up the proposed system. In effect, it shows a

concede picture of how these component function in relation to one another and

how the business document are interchanged.

22
 There are two main type of Electronic Data Interchange, the web based

EDI, where Value Added Network (VAN) are used to transmit document over

the internet and local base EDI where software are performing the duties of

VAN in Local Area Network (LAN).

Customer Interface

EDI Software Secure

server

Processing Customer Order

SQL
Software
Database

Fig. 3.1 EDI Architecture

The diagram above shows the working relation of the subsystem. An

Electronic Data interchange interface consists of the following subsystem:

1. Customer interface: This is also referred to as the user interface (UI)

where the customers interact with EID software during the process of

document transition. The customer interface consists of the following

forms:

i. Login Form: This is a form that allows registered or old customers

to log in to the secure server for proper verification before they can

23
 order for products. In this form, customer’s company name and their

password will be supplied.

ii. Registration form: This is a form that allows new customers to

register with the company for proper identification, so that they can

order for product.

iii. Order form: This form contains products that you can order and it

also contains a list they can order for products.

2. EDI Software: This is a software that performs the transmission of the

business documents like the submission and sends confirmation

messages. Costumer order list, Invoice, Identity notification slip, receipt

etc. In the proposed EDI system, it is the logic behind the EDI interface.

3. Secure Server: This is a unique machine or computer in the network that

manipulates all other customer computers in the network. This is where

the secure SQL database and the store procedure that process the

customer order reside.

4 SQL Database: This is an object that stores structured complex

information in a table whether related or unrelated. For the purpose of this

project work, a SQL database is designed to store customer’s information

ordering information, product information.

Therefore our database will consist of three tables namely:

i. Customer table

ii. Order table

iii. Product table

24
 i. Customer Table: This table stores information about a customer,

Information like customer’s ID, Customer’s company name,

Customer’s password, Customer’s address, Customer’s phone

Number etc. All these information are required before a customer

can place an order for a product.

ii. Order Table: The order table will store information about

customer’s order like, ID, price, Quantity, discount, date of order

and so on. All these information are needed to prepare the

customer order for shipment.

iii. Product Table: This table stores information about the product

purchased by the customer. This information includes: product ID,

product name and price.

5. Processing Customer’s Order: This is stored procedure that resides in

the database to process customer’s order, it is written in structured query

language (SQL) to query the database and send report to the customer.

Report in this context refers to as business document like order lists,

invoice receipt etc.

3.04 SYSTEM SPECIFICATION

The new system should be able to meet the standard outlined below to

achieve the full aim of an EDI.

1. It must be able to connect to the main database server in the network.

2. It must have a gate way to the local network.

3. It must be easy to Implement and use.

25
4. It must be available at all time irrespective of power failure.

5. It must be reliable and have record of being fully operational of at least

99% of the time.

6. It must provide a level of performance adequate to ensure the 99% of all

business documents transmitted and the remaining 10% are received

within two hours.

3.05 SYSTEM DESIGN

Following the discussion of section 3.4.1 above, module design is

employed. The problem is broken down into sub-problems and each sub-

program is handled by a procedure within the program code as will be seen

later in chapter four.

26
 CHAPTER FOUR

PROGRAM IMPLEMENTATON

Implementation is the process of converting system specification in

chapter three into a set of programs or program unit.

4.00 THE CHOICE OF PROGRAMMING LANGUAGE USED

The choice of programming language used to implement this EDI for

business situations is Microsoft Visual Basic (MS V .B.NET).

Visual basic is the most recent Microsoft programming language product;

it is an object oriented programming language that runs all platforms in the

computing world. It is very efficient in designing business base software such

as this because of its functionality, and it Integrated Development Environment

(IDE) for designing a very interactive graphic user interface (GUI), Most

programmers use it to develop application in all ratification Vb.net is simple to

learn. To start using Visual Basic, Effective programming skills is not necessary

because it drags and drops window, controls when designing an interface for

an application. It runs on a platform of Vb.net framework. It can be used to

develop Windows application, Web application, Customer controls, information

internet service (IIS) and Data base etc.

Therefore, because of all these functionality and factors, I decide to adopt

it in this project work.

27
4.01 PROGRAM SPECIFICATION

Program specification is the act of using system specification or

requirement in chapter three to develop the structure and logic of the program

thereby identifying the task involved.

This must be accomplished by a program in order to be able to perform

the function of electronic data interchange (EDI).

This is printing out business document for the customers and accepting

business data from customers etc. the question is how would this program be

implemented in situation?

Some of the basic requirements for the effective improvement of this

system includes:-

i. The effectiveness of the programming language used in t he business

situation.

ii. The programming approach being employed.

iii. The hardware and operating system available.

iv. The effectiveness of the database management system (DBMS) used to

create the database involved. With proper organization of the listed

above, the efficacy and smooth running of the program will be guarantee.

4.02 PROGRAM DESCRIPTION

28
 Thus, program is set out to transact business with customers and

interchange business documents based on the conventional transaction of

business (that is paper from one office to another).

This software performs the functionality of an EDI that is it can transact

business and interchange business document with the interface.

4.2.1 PROGRAM FLOWCHART

The process of program design is to organize into logical order the

necessary stages involve in the solution to this project work.

When the design is completed, it is given a desk-check to see whether it

is feasible and if it will produce the desire result. If the design is correct logically

and otherwise, we digress into program coding. Below is the flowchart:

29
 USER FLOWCHART

START

INPUT USERNAME &

PASSWORD

PROCESS USERNAME REGISTRATION

AND PASSWORD PAGE

USER FOUND

ORDER ITEMS

PRINT ORDER
SUCCESSFUL

STOP

30
Figure 4.2.1 User Flowchart

ADMIN FLOWCHART

START

INPUT USERNAME &

PASSWORD

PROCESS USERNAME
AND PASSWORD

YES NO
PASSWORD
VALID

GRANT
ACCESS
STOP

Figure 4.2.1 Administrator Flowchart

4.4.2 PROGRAM LAYOUT AND FUNCTIONALITY

There are four Graphic user interface forms (GUI) within this program.

They are listed below:

1. Main form user interface;

31
 2. Logic form user interface;

3. Order form user interface; and

4. Register form user interface.

Main form user interface: This interface is called the main form because this

is the form interface that will lead you to all other interface in the program or

software. The main interface consists of one menu called the file menu and a

button that triggers the login form interface when clicked. The file menu

consists of three submenus:

 Customer submenu, which contains two submenus new and existing.

 Print submenu which is use to trigger the print dialog box if customer want

to print out business document

 Exit sub menu which close the software, or terminate the software

Login form interface: The main function of this interface is to restrict customer

who did not register to order for products. This is because all customers must

register before they can order for product using this software.

The login form interface consists of two text boxes where establishment

can enter their customer’s name and password and two buttons where you can

either login to order products or quit login form.

Order Form Interface: This interface is a form which customers fill to specify

their order requirement. It consists of text boxes, combo boxes, and buttons for

the customers to interact with the database. The main function of this form is to

order for products in stock.

32
Register Form Interface: All new customers must register first before they can

place order for products in stock. The register form interface is like a form

where you supply your data to the database for recognition in case you want to

order for products.

Print Dialog Box: This is a dialog box that is used to specify the type of

documents you want to print using the default print. It is like every other window

application print dialog box.

4.03 VISUAL BASIC.NET EVENT HANDLER

In VB programming environment, all windows control like buttons,

textboxes, label combo boxes e.t.c. have their own program segment or

program modules called event handler.

Event handler handles events for a particular window subprogram or

module and trigger the respective event. Examples of Event handler in VB are:

1. Click;

2. Mouse over;

3. Double click;

4. Key press down;

5. Key press up etc.

These entire event handlers have a code behind their window controls that

trigger those listed above.

33
 In this project work, some of the window controls like button event handler

will be discussed in all the sub programs.

1. Main form sub program events:

a. Button Click Event: This event triggers the login form when clicked.

b. Menu Item 3 Click: This event triggers the register form when

clicked.

c. Menu Item 4: This event triggers the order form interface when

clicked.

d. Menu item 10 clicks: this event calls an end method to terminate the

entire program.

2. Register form sub program event button: This event triggers the

method that enables you to connect to the SQL Database for processing

of customer registration.

a. Button 3 click Event: This event calls the method that close the

register form interface.

b. My Base Load Event: This event opens a connection to the

database.

3. Order form sub program event:

a. Button 3 Click Event: This event triggers the submission of order to

the database.

b. Button 3 Click Event: This event cancels the order made by the

customer.

34
 c. Textbox 3. Click Event: This event display the unit price to the

textbox when clicked etc.

4. Login form sub program event:

a. Button 3 click Event: This event trigger the order form of your

customer name and password are correct.

b. Button 1. click Event: This event calls the close method to close the

login form interface

4.04 EDI IMPLEMENTATION

Depending on the types of solution chosen, EDI implementation can be

achieved almost immediately. For web-bases EDI solutions chosen by an

organization require that all customer or client that will use the software will

have to fill out necessary online form via their web portal before sending the

required documents. Utilizing more complex system often requires that EDI

software be installed on your company’s network. This allows for EDI

integration with your company’s back-end office systems. As you begin trading

with more partners and you will experience business growth, your EDI system

will grow in complexity as such, an EDI system is an evolution solution.

35
 CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATION
5.00 SUMMARY
Electronic data interchange is a tool which is at the heart of electronic

commerce activity. Using the carefully constructed standards which have been

developed and which continue to evolve into a single set of internationally

recognized standards establish a firm communications base for electronic

business transactions. The financial benefits which accrue from using these

methods are substantial. Many companies have pioneered and perfected the

use of electronic data interchange interface methods on their mainframe

computers and many have elected to use the services of the value added

network service providers. EDI has successfully replaced paper document,

eliminating the inefficiencies of manual system.

5.01 CONCLUSION

In conclusion, Electronic Data Interchange (EDI) serves as tools to

improve the business process that flow between organizations. It reduces cost,

delays and error inherent in manual delivery system of document.

5.02 RECOMMENDATION

36
 The amount of experience you need in order to be able to do EDI directly

correlates to the type of EDI solution you choose for your business. Generally,

specific experience is not needed. With Internet – based EDI, solutions are

typically “hosted” by a company. All that is needed to access this type of EDI

system is an internet connection and a web browser. Web – based EDI is the

simplest method of EDI interaction. For EDI software implementation, simple

training is often recommended for your employees. Your EDI vendor can

provide this training.

EDI is highly recommended due to the above reasons. The chief benefits
of using electronic data interchange will be accomplished as:

 Decreasing the potential source of error caused by re-entry of data and

handing paper involved in orders and accounts processing, reducing

postage bills, and manual processing costs involved with paper filing

systems.

 Shortening the lead time between receipt and fulfillment of orders as well

as helping to plan production and reduce stocks of inventories.

 Providing trading information from historical data accumulated as a result

of using electronic data interchange transactions to gain a competitive

edge.

 Enhancing the image of the company and increasing the company’s

ability to provide faster and better customer service.

5.03 SUGGESTIONS

37
 During the course of this project work some data and authentication

document were not implemented for interchange such as signature, company

certificate, type of payment. The foundation has already been laid for EDI

standard format and data encryption of password. For further researchers I will

suggest that they should try in their software to implement them.

38
 REFERENCES

Cain, R.J. (2000) Value-added networks: What to look for now and in the future.
Conference Proceedings EDI: EDI, Electronic Commerce, and You; (pp. 141 -
157).

Cavalli. A. (1995) “Electronic Commerce over the Internet and the Increasing Need
for Security” December 8,
http://www.galaxy.einet.net/tradewave/products/vpiwp.html.

Gary .P, Schneider .J, Perry .T: (1979) Electronic Commerce University of san diego

Haynes T. (1995): The Electronic Commerce Dictonary: The Definitive Terms for
Doing Business on the Information Highway. California: Robleda Company. (2 nd
Edition).

Kumar, Ram and Connie W.C (1996): “Educating Senior Management on the
Strategic Benefits of Electronic Data Interchange. “ Journal of Systems
Management, March-April, Pg42-48.

Kimberley P. (1991). EDI. New York: McGraw-Hill.

Nelson .D, Chris K. “The ABC of EDI,” UK/EDI Awareness Centres,

http://www.imaginet.co.uk/edi/features4.html

Philipus .G, Michael D. (April 1998): “Applying Electronic Data Interchange”. Risk
management

39
Sawabini, S. (1995). Introduction to EDI. Conference Proceeding EDI 2000:EDI, EC
and You, (pp. 1-36).

Sokol, P. K. (1995). From EDI to EC: A business Initiative. New York: McGraw-Hill.

APPENDIX I

40
SPLASH SCREEN

CONTACT PAGE

41
PRODUCT PAGE

LOGIN PAGE

42
REGISTRATION PAGE

43
ORDER PAGE

44
CUSTOMERS ORDER PAGE

45
VIEW PRODUCT PAGE

ADD PRODUCTS PAGE

46
ADMIN PAGE

ADMIN HOME PAGE

47
APPENDIX II

48
//ADD PRODUCT PAGE

Imports System.Data.OleDb

Public Class AddProducts

Private Sub btnAddCategory_Click(sender As Object, e As EventArgs) Handles

btnAddCategory.Click
Dim conn As OleDbConnection
conn = New OleDbConnection
'conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection

Try
Dim InsertCommand As String
InsertCommand = "INSERT INTO [Products]
(ProductCategory,ProductName,ProductDescription,UnitPrice) VALUES('" +
dpdProductCategory.SelectedValue + "','" + txtProductName.Text + "','" + txtProductDescription.Text
+ "','" + txtUnitPrice.Text + "')"
Dim cmd As OleDbCommand
cmd = New OleDbCommand(InsertCommand, conn)
conn.Open()
cmd.ExecuteNonQuery()
lblStatus.Text = "Product Added Successfully..."
conn.Close()
Catch ex As Exception
lblStatus.Text = ex.Message
End Try

End Sub

Private Sub btnCloseForm_Click(sender As Object, e As EventArgs) Handles btnCloseForm.Click

AdminHomePage.Show()

Me.Hide()

End Sub

Private Sub AddProducts_Load(sender As Object, e As EventArgs) Handles MyBase.Load

'TODO: This line of code loads data into the 'EDIdbPCategoryDS.ProductsCategory' table. You
can move, or remove it, as needed.
Me.ProductsCategoryTableAdapter.Fill(Me.EDIdbPCategoryDS.ProductsCategory)

End Sub
End Class

//ADMIN HOME PAGE

Public Class AdminHomePage

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

AddEditCategory.Show()

Me.Hide()

End Sub

49
 Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
AddProducts.Show()

Me.Hide()

End Sub

Private Sub btnLogOut_Click(sender As Object, e As EventArgs) Handles btnLogOut.Click

AdminLogIN.Show()
Me.Hide()
End Sub
Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click
Application.Exit()
End Sub
Private Sub btnAdminLogIn_Click(sender As Object, e As EventArgs) Handles
btnAdminLogIn.Click
ViewOrders.Show()

Me.Hide()
End Sub

Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click

AddAdminUser.Show()
Me.Hide()

End Sub
Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button5.Click
viewProducts.Show()

Me.Hide()

End Sub

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

System.EventArgs) Handles MyBase.Load

End Sub
End Class

//DEFAULT PAGE

Public Class Form1

Private Sub btnExit_Click(sender As Object, e As EventArgs) Handles btnExit.Click

Application.Exit()

End Sub

Private Sub btnAdminLogIn_Click(sender As Object, e As EventArgs) Handles

btnAdminLogIn.Click
AdminLogIN.Show()

Me.Hide()

50
 End Sub

Private Sub btnContactUs_Click(sender As Object, e As EventArgs) Handles btnContactUs.Click

ContactUs.Show()

Me.Hide()

End Sub

Private Sub btnOurService_Click(sender As Object, e As EventArgs) Handles btnOurService.Click

Ourservices.Show()

Me.Hide()

End Sub

Private Sub btnUsersRegisteration_Click(sender As Object, e As EventArgs) Handles

btnUsersRegisteration.Click
UsersRegistrationPage.Show()

Me.Hide()

End Sub

Private Sub btnUsersLogIn_Click(sender As Object, e As EventArgs) Handles btnUsersLogIn.Click

UsersLogIn.Show()

Me.Hide()

End Sub

Private Sub Label3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles Label3.Click

End Sub

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load

End Sub
End Class

//USER REGISTRATION PAGE

Imports System.Data.OleDb
Imports System.Configuration
Public Class UsersRegistrationPage
Private Sub btnAddCategory_Click(sender As Object, e As EventArgs) Handles
btnAddCategory.Click
Dim conn As OleDbConnection
conn = New OleDbConnection
'conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection
Try
Dim InsertCommand As String

51
 InsertCommand = "INSERT INTO [Users]
(UFirstName,UOtherNames,USex,UDob,UState,UNationality,UPhone,UEmail,UPHomeAddress,UUs
erName,UPassword) VALUES('" + txtFirstName.Text + "','" + txtOtherNames.Text + "','" +
dpdSex.SelectedValue + "','" + txtDOB.Text + "','" + dpdState.SelectedValue + "','" +
txtNationality.Text + "','" + txtPhone.Text + "','" + txtEmailAddress.Text + "','" + txtHomeAddress.Text
+ "','" + txtUserName.Text + "','" + txtPassword.Text + "')"
Dim cmd As OleDbCommand
cmd = New OleDbCommand(InsertCommand, conn)
conn.Open()
If txtPassword.Text <> txtConfirmPassword.Text Then
MessageBox.Show("Both Password Must Match!")
txtConfirmPassword.Text = String.Empty
txtPassword.Text = String.Empty
txtPassword.Focus()
Return

Else
cmd.ExecuteNonQuery()
lblStatus.Text = "Registration Successful! Please Log In to Continue"
conn.Close()
End If

Catch ex As Exception
lblStatus.Text = ex.Message

End Try
End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

txtConfirmPassword.Text = ""
txtNationality.Text = ""
txtFirstName.Text = ""
txtOtherNames.Text = ""
dpdSex.Text = ""
dpdState.Text = ""
txtHomeAddress.Text = ""
txtEmailAddress.Text = ""
txtPhone.Text = ""
txtUserName.Text = ""

End Sub

Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click

Form1.Show()

Me.Hide()

End Sub

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

System.EventArgs) Handles MyBase.Load

End Sub
End Class

//ORDERS PAGE
52
Imports System.Data.OleDb

Public Class OrdersPage

Private Sub btnSubmit_Click(sender As Object, e As EventArgs) Handles btnSubmit.Click

Dim conn As OleDbConnection
conn = New OleDbConnection
' conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection

Try
Dim INsertCommand As String
INsertCommand = "INSERT INTO [ORDERS]
(UserName,ProductName,ODescription,OQty,ShipAddress,Country,City,OState,ZipCode,AreaCode)
VALUES('" + txtUserName.Text + "','" + txtProduct.Text + "','" + txtProductDescription.Text + "','" +
txtQuantity.Text + "','" + txtShipAddress.Text + "','" + txtCountry.Text + "','" + txtCity.Text + "','" +
dpdState.SelectedItem + "','" + txtZipCode.Text + "','" + txtAreaCode.Text + "')"
Dim cmd As OleDbCommand
cmd = New OleDbCommand(INsertCommand, conn)
conn.Open()
cmd.ExecuteNonQuery()
lblStatus.Text = "Order Has Been Submitted, And Will Be Delivered Within 72 Hours. Thank
You!"
conn.Close()

Catch ex As Exception
lblStatus.Text = ex.Message

End Try
End Sub

Private Sub btnResetForm_Click(sender As Object, e As EventArgs) Handles btnResetForm.Click

txtAreaCode.Text = ""
txtUserName.Text = ""
txtCity.Text = ""
txtCountry.Text = ""
txtProduct.Text = ""
txtProductDescription.Text = ""
txtQuantity.Text = ""
txtShipAddress.Text = ""
txtUserName.Text = ""
txtZipCode.Text = ""
dpdState.Text = ""

End Sub

Private Sub btnExit_Click(sender As Object, e As EventArgs) Handles btnExit.Click

UsersHomePage.Show()

Me.Hide()

End Sub

Private Sub OrdersPage_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
53
 End Sub
End Class

//ADMIN LOGIN PAGE

Imports System.Data.OleDb

Public Class AdminLogIN

Private Sub btnCancel_Click(sender As Object, e As EventArgs)
Form1.Show()
Me.Hide()

End Sub

Private Sub btnClickMe_Click(sender As Object, e As EventArgs) Handles btnClickMe.Click

Dim conn As OleDbConnection
conn = New OleDbConnection
'conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection
Try
Dim SelCOmmand As String
SelCOmmand = "SELECT [UserName],[Password] FROM Admin Where UserName ='" +
txtUserName.Text + "' AND [Password] ='" + txtPassword.Text + "'"
Dim cmd As OleDbCommand
conn.Open()

cmd = New OleDbCommand(SelCOmmand, conn)

Dim dr As OleDbDataReader
dr = cmd.ExecuteReader
If (dr.HasRows) Then
While (dr.Read())
AdminHomePage.Show()
Me.Hide()
End While
dr.Close()
conn.Close()

Else
lblStatus.Text = "Invalid Log In Parameter"
txtPassword.Text = ""
txtUserName.Text = ""
txtUserName.Focus()

End If
Catch ex As Exception
lblStatus.Text = ex.Message

End Try

End Sub

Private Sub brnLogIn_Click(sender As Object, e As EventArgs)

End Sub
Private Sub btnExit_Click(sender As Object, e As EventArgs) Handles btnExit.Click
Form1.Show()
54
 Me.Hide()
End Sub
Private Sub AdminLogIN_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles MyBase.Load
End Sub
End Class

//ADD ADMIN USER PAGE

Imports System.Data.OleDb

Public Class AddAdminUser

Private Sub btnSubmit_Click(sender As Object, e As EventArgs) Handles btnSubmit.Click

Dim conn As OleDbConnection
conn = New OleDbConnection
'conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection
Try
Dim InsertCommand As String
InsertCommand = "INSERT INTO [Admin] ([FullName],[Sex],[Role],[UserName],[Password])
VALUES('" + txtFullName.Text + "','" + dpdSex.SelectedItem + "','" + dpdRole.SelectedItem + "','" +
txtUserName.Text + "','" + txtPassword.Text + "')"

Dim cmd As OleDbCommand

cmd = New OleDbCommand(InsertCommand, conn)
conn.Open()
cmd.ExecuteNonQuery()
lblStatus.Text = "Admin User Added Successfully"
conn.Close()

Catch ex As Exception
lblStatus.Text = ex.Message
End Try
End Sub

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

AdminHomePage.Show()

Me.Hide()

End Sub

Private Sub AddAdminUser_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load

End Sub
End Class

//VIEW ORDERS PAGE

Public Class ViewOrders

Private Sub ViewOrders_Load(sender As Object, e As EventArgs) Handles MyBase.Load

55
 'TODO: This line of code loads data into the 'EDIdbViewOrdersDS.Orders' table. You can move,
or remove it, as needed.
Me.OrdersTableAdapter.Fill(Me.EDIdbViewOrdersDS.Orders)

End Sub

Private Sub btnBack_Click(sender As Object, e As EventArgs) Handles btnBack.Click

AdminHomePage.Show()

Me.Hide()

End Sub
End Class

//CONTACT US PAGE
Public Class ContactUs

Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click

Form1.Show()

Me.Hide()

End Sub

Private Sub ContactUs_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load

End Sub
End Class

//VIEW PRODUCT PAGE

Public Class viewProducts
Private Sub viewProducts_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles MyBase.Load
'TODO: This line of code loads data into the 'ProductListDS.Products' table. You can move, or
remove it, as needed.
Me.ProductsTableAdapter.Fill(Me.ProductListDS.Products)
End Sub
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button1.Click
AdminHomePage.Show()
Me.Hide()

End Sub
End Class
//USER HOME PAGE
Public Class UsersHomePage
Private Sub Button2_Click(sender As Object, e As EventArgs)
End Sub
Private Sub btnPlaceOrder_Click(sender As Object, e As EventArgs) Handles btnPlaceOrder.Click
OrdersPage.Show()

Me.Hide()

End Sub

56
 Private Sub btnLogOut_Click(sender As Object, e As EventArgs) Handles btnLogOut.Click
UsersLogIn.Show()

Me.Hide()

End Sub

Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click

Application.Exit()

End Sub

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

System.EventArgs) Handles MyBase.Load

End Sub
End Class

//USER LOGIN PAGE

Imports System.Data.OleDb
Public Class UsersLogIn
Private Sub Button1_Click(sender As Object, e As EventArgs)
End Sub

Private Sub btnLogIn_Click(sender As Object, e As EventArgs) Handles btnLogIn.Click

Dim conn As OleDbConnection
conn = New OleDbConnection
'conn.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Users\
D'Prince\Documents\Visual Studio 2012\Projects\JohnEDIVB\Database\EDIdb.accdb;"
conn.ConnectionString = My.Settings.EDIConnection
Try
Dim SelCOmmand As String
SelCOmmand = "SELECT UUSERNAME,UPassword FROM USERS Where UUserName ='"
+ txtUserName.Text + "' AND UPassword ='" + txtPassword.Text + "'"
Dim cmd As OleDbCommand
conn.Open()
cmd = New OleDbCommand(SelCOmmand, conn)
Dim dr As OleDbDataReader
dr = cmd.ExecuteReader
If (dr.HasRows) Then
While (dr.Read())
UsersHomePage.Show()
Me.Hide()
End While
dr.Close()
conn.Close()

Else
lblStatus.Text = "Invalid Log In Parameter"
txtPassword.Text = ""
txtUserName.Text = ""
txtUserName.Focus()

End If
Catch ex As Exception
lblStatus.Text = ex.Message
End Try
57
 End Sub
Private Sub btnClose_Click(sender As Object, e As EventArgs) Handles btnClose.Click
Form1.Show()
Me.Hide()

End Sub

Private Sub UsersLogIn_Load(ByVal sender As System.Object, ByVal e As System.EventArgs)

Handles MyBase.Load
End Sub
End Class

//ADMIN HOME PAGE

Public Class AdminHomePage
Private Sub Button2_Click(sender As Object, e As EventArgs) Handles Button2.Click
AddEditCategory.Show()
Me.Hide()
End Sub
Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
AddProducts.Show()
Me.Hide()
End Sub
Private Sub btnLogOut_Click(sender As Object, e As EventArgs) Handles btnLogOut.Click
AdminLogIN.Show()
Me.Hide()
End Sub
Private Sub Button3_Click(sender As Object, e As EventArgs) Handles Button3.Click
Application.Exit()
End Sub
Private Sub btnAdminLogIn_Click(sender As Object, e As EventArgs) Handles
btnAdminLogIn.Click
ViewOrders.Show()
Me.Hide()
End Sub
Private Sub Button4_Click(sender As Object, e As EventArgs) Handles Button4.Click
AddAdminUser.Show()
Me.Hide()
End Sub
Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles Button5.Click
viewProducts.Show()
Me.Hide()
End Sub
Private Sub AdminHomePage_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles MyBase.Load
End Sub
End Class.

58