2016

CD Management]

PROJECT OVERVIEW

The main object of CD Management software is computerized the Purchasing department of an

organization.

This software primarily focuses on the entry of CD details of It aims to realize the following
processes and database requirements:

Recording, storage, retrieval and manipulation of cd details of the Purchase CD.

It provides keeping record on computer of the Received cd at time to time. It manages

when CD received, what is the rate of cd and how much quantity received.

It also keeps record on computer of the Issued product from the stock. It manages how
much CD issued.

It maintains how much quantity on hand at that time.

Creation of master database storing cd-details.

Generation and issue periodical reports including cd Details, Received CD and issue CD
details etc.

Information retrieval via screens and customized reports.

Objectives

Keeping in view, the computerization’s vast scope for data collection, storage, processing and
retrieval, effective and proper maintenance of CD is well with in its purview. Generation of Data
integrity, accuracy and timeliness in case processing is ensured.
Speed up the process of Product Received and Issued.
To bring transparency & easy and speedy access to product status.
Data Safety by using proper backup management and Disaster recovery management
techniques
 2016
CD Management]

SCOPE OF PROJECT

This Database System is a P.C. Based system. This System is capable of processing the transaction of
data base activity along with the transaction processing. The system is also capable of generating
various reports database. It can also generate various documents involved in the database activity.
With the help of this system user can take quick decision by referring to the reports generated by
this system. It also helps in easy flow of works in the department, which is a very important task.
This is the only channel through which one can build a network of database and gain maximum
advantages and in this activity this system plays a very important role.

The whole Software has been developed according to the user requirements hence it may not be
according to the norms that is to be followed while preparing good software.
Still to the best of my knowledge it fulfills all the requirements of the concerned Organization and
hence the ultimate goal of undergoing this process is being met.
To provide checking of data Most of the problems in the system are due to erroneous data
entry. If this checked at the entry level itself, the process will be streamlined, accurate and
faster.
To make the system user friendly the system as designed in such a manner that user finds it
easy to operate i.e. user get the facility of GUI (Graphical User Interface).
Display of Message are provided by the system which proves to be useful for the user i.e. if user
makes any error the system displays error message to alert the user from making mistakes in
data entry.
To provide Menu-driven system. The system provides menu interface i.e. it is entirely menu
driven which as many option to choose which gives the user an opportunity. User can operate
by choosing options on selection bar. Thus it makes the task easier for the user who has less or
no experience to handle the system.
To provide security aspects. The meaning of security is to provide a detective access to the
programmers and database. Providing for the system achieves this purpose.
 2016
CD Management]

PROBLEM IN EXISTING SYSTEM

The existing system of the CD purchasing is running expeditiously on Manual Interface, which is
bound to human errors and omissions.
Lot of Book Keeping and Ledger entries have to be done manually, investing a huge amount in
stationary and human labor.
It is a big task to lookup the item database by finding the concerned register or ledger.
Redundancy of human errors is expected that leads to contra entry and replication of database.
Overall it can be concluded that although the management is running successfully on manual
interface work, but a need to switch to electronic processing is highly deemed.

BENEFITS OF NEW SYSTEM

Single interface user friendly environment.

Fast Processing & display.

Record Keeping made easy and one step.

Ease of work due to less manual works.

High Quality Reports Generation in a second according to any queries .

No dependency to any other application or ledger.

Back Up of records and data recovery extended.

To provide security aspects. The meaning of security is to provide a detective access to the

programmers and database. Providing for the system achieves this purpose.
 2016
CD Management]

DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the “flow” of data through an
information system. A data flow diagram can also be used for the visualization of data processing
(structured design). It is common practice for a designer to draw a context-level DFD first which
shows the interaction between the system and outside entities.

In analyzing a business, several sets of DFD’s are drawn. Initial DFD’s might model the existing
system (flaws and all), while later DFD’s may model a solution to the problem being analyzed. For
these solution DFD’s a logical and physical DFD is drawn. Physical DFD’s represent physical files and
transactions, while logical or conceptual DFD’s can be used to represent business functions or
processes.

The four components of a data flow diagram (DFD) are:

External Entities/Terminators

are outside of the system being modeled. Terminators represent where information
comes from and where it goes. In designing a system, we have no idea about what
these terminators do or how they do it.

Processes

Modify the inputs in the process of generating the outputs Data Stores A DFD does
not say anything about the relative timing of the processes, so a data store might be
a place to accumulate data over a year for the annual accounting process.

Data Flows

are how data moves between terminators, processes, and data

stores.

In analyzing a business, several sets of DFD’s are drawn. Initial DFD’s might model
the existing system (flaws and all), while later DFD’s may model a solution to the
problem being analyzed. For these solution DFD’s a logical and physical DFD is
 2016
CD Management]
drawn. Physical DFD’s represent physical files and transactions, while logical or
conceptual DFD’s can be used to represent business functions or processes.

Data Flow Diagram (DFD) of CD Purchase System

 2016
CD Management]

STEPS IN DESIGNING DATABASE

Determine the purpose of your databases

Determine the tables you need in the database

Determine the fields you need in the table

Identify fields with unique values in each record

Determine the relationships between tables

Refine your design

Enter data and create other database objects

DETERMINE THE PURPOSE OF YOUR DATABASE

The first step in designing databases is to determine its purpose and how it’s to be used. You need
to know what information you want from the database. From that, you can determine what
subjects you need to store facts about (the tables) and what facts you need to store about each
subject (the fields in the tables) .

Talk to people who will use the database. Brainstorm about the questions you and they would like
the database to answer. Sketch out the reports you’d like it to produce. Gather the forms you
currently use to record your data. Examine well-designed databases similar to the one you are
designing.

DETERMINE THE TABLES YOU NEED

Determining the tables can be the trickiest step in the database design process. That’s because the
results you want from your database --the reports you want to print .the form you want to use, the
questions you want answered -don't necessarily provide clues about the structure of the tables that
produce them.

You don't need to design your tables using Microsoft Access. In fact, it may be better to sketch out
and rework your design on paper first. When you design your tables, divide up pieces of
information by keeping these fundamental design principles in mind:
 2016
CD Management]
A table should not contain duplicate information, and information should not be duplicated
between tables. In this respect, a table in a relational database differ form a table in a flat-file
application such as a spreadsheet.

When each piece of information is stored in only one table, you update it in one place. This is
more efficient, and it also eliminates the possibility of duplicate entries that contain different
information. For example, you would want to store each customer address and phone number
only once, in one table.

Each table should contain information about one subject.

When each table contains facts about only one subject, you can maintain inform motion about
each subject independently from other subject. For example, you would store customer
addresses in a deferent table from the customer's orders, so that you could delete one order
and still maintain the customer information.

DETERMINE THE FIELDS YOU NEED

Each table contains information about the same subject, and each field in a table contains
individual facts about the table’s subject. For example, a customer table may include company
name, address, city, state and phone number fields. When sketching out the fields for each table,
keep these tips in mind:

Relate each fields directly to the subject of table.

Don’t include derived or calculated data (data that is the result of an expression).

Include all the information you need.

Store information in its smallest logical part (for example, First Name and Last Name,
rather than Name).

IDENTIFY THE FIELD OR FIELDS WITH UNIQUE VALUES IN EACH RECORD

In order for Microsoft Access to connect information stored in separate tables —for example, to
connect a customer with all the customer’s order—each table in your database must include a field
or set of fields that uniquely identifies each individual record in the table. Such a fields that
uniquely identifies each individual record in the table. Such a field or set of fields is called a primary
key.
 2016
CD Management]

DETERMINE THE RELATIONSHIPS BETWEEN TABLES

Now that you’ve divided your information into tables and identified primary key fields, you need a
way to tell Microsoft Access how to bring related information back together again in meaningful
ways. To do this, you define relationships between tables in a Microsoft Access database.

REFINE YOUR DESIGN

After you have designed the tables, fields and relationships you need, it’s time to study the design
and detect any flaws that might remain. It is easier to change your database design now than it will
be after you have filled the tables with data. Use Microsoft Access to create your tables ,specify
relationships between the tables, and enter enough sample data in your tables so you can test your
design. To test the relationships in your database, see if you can create queries to get the answers
you want. Create rough drafts of your forms and reports and see if they show the data you expect .
Look for unnecessary duplications of data and eliminate them. If you find problems. refine the
design.

ENTER DATA AND CREATE OTHER DATABASE OBJECTS

When you are satisfied that the table structures meet the design principles described here, then it’s
time to go ahead and add all your existing data to the tables. You can then create any queries,
forms, reports, data access pages, macros, and modules that you may want. See a comparison of
database object in Microsoft Access project and database object in an Access database.
 2016
CD Management]

DATA DICTIONARY
A data dictionary is a set of metadata that contains definitions and representations of data
elements.

Table Name: User_Master

FIELD NAME DATA TYPE SIZE REMARK

Username Text 20 Not Null

Password Text 10 Not Null

Table Name: Supplier_Master

FIELD NAME DATA TYPE SIZE REMARK

SID Number 3 Primary Key

SupplierName Text 100 Not Null

SupplierAddress Text 100

Contact No Text 50

TinNo Number 15 Not Null

Table Name: Company_Master

FIELD NAME DATA TYPE SIZE REMARK

CID Number 3 Primary Key

CompanyName Text 100 Not Null

CompanyAddress Text 100

Contact No Text 50
 2016
CD Management]

Table Name: CD_Master

FIELD NAME DATA TYPE SIZE REMARK

EID Number 4 Primary Key

E_Name Text 100 Not Null

E_Type Text 50 Not Null

CompanyId Number 5 -

Rate Number 10,2 -

M_Unit Text 15 -

Table Name: Purchase_Order_Master

FIELD NAME DATA TYPE SIZE REMARK

PO_No Text 25 Primary Key

PO_Date Date - Not Null

CD Id Number 3 Foreign Key

Order_Qty Number 5 Not Null

Rate Number 10,2

SupplierId Number 3 Foreign Key

Auth_Person Text 50 Not Null

Table Name: Equ_Purchase_Rec

FIELD NAME DATA TYPE SIZE REMARK

PO_No Text 25 Foreign Key

Rec_Date Date - -

Rec_Qty Number 5 Not Null

Remark Text 25 -
 2016
CD Management]

Table Name: Equ_Issue

FIELD NAME DATA TYPE SIZE REMARK

Equ_ID Number 4 Foreign Key

Issue_Date Date - -

Issue_Qty Number 5 -

Issued_By Text 25 -

Remark Text 20 -
 2016
CD Management]

SOFTWARE DEVELOPMENT PROCESS

A software development process is a structure imposed on the development of a software product.
Synonyms include software life cycle and software process.

The software concept - identifies and defines a need for the new system.

A requirements analysis - analyzes the information needs of the end users.

The architectural design - creates a blueprint for the design with the necessary specifications for
the hardware, software, people and data resources.

Coding and debugging - creates and programs the final system.

System testing - evaluates the system’s actual functionality in relation to expected or intended
functionality.

Process Activities/Steps

Software Engineering processes are composed of many activities, notably the following. They are
considered sequential steps in the Waterfall process, but other processes may rearrange or
combine them in different ways.

Requirement Analysis

Extracting the requirements of a desired software product is the first task in creating it. While
customers probably believe they know what the software is to do, it may require skill and
experience in software engineering to recognize incomplete, ambiguous or contradictory
requirements.

Specification

Specification is the task of precisely describing the software to be written, in a mathematically

rigorous way. In practice, most successful specifications are written to understand and fine-tune
applications that were already well-developed, although safety-critical software systems are often
carefully specified prior to application development. Specifications are most important for external
interfaces that must remain stable.

Software Architecture

The architecture of a software system refers to an abstract representation of that system.

Architecture is concerned with making sure the software system will meet the requirements of the
 2016
CD Management]

product, as well as ensuring that future requirements can be addressed. The architecture step also
addresses interfaces between the software system and other software products, as well as the
underlying hardware or the host operating system.

Coding

Reducing a design to code may be the most obvious part of the software engineering job, but it is
not necessarily the largest portion.

Testing

Testing of parts of software, especially where code by two different engineers must work together,
falls to the software engineer.

Documentation

An important (and often overlooked) task is documenting the internal design of software for the
purpose of future maintenance and enhancement. Documentation is most important for external
interfaces.

Maintenance

Maintaining and enhancing software to cope with newly discovered problems or new requirements
can take far more time than the initial development of the software. Not only may it be necessary
to add code that does not fit the original design but just determining how software works at some
point after it is completed may require significant effort by a software engineer. About 2/3 of all
software engineering work is maintenance, but this statistic can be misleading. A small part of that
is fixing bugs.
 2016
CD Management]

FEASIBILITY STUDY

A feasibility study is a preliminary study undertaken before the real work of a project starts to
ascertain the likelihood of the project’s success. It is an analysis of all possible solutions to a
problem and a recommendation on the best solution to use. The purpose of a feasibility study is to
determine whether or not the purpose of a new system can be justified.

Feasibility Viewpoint

Economic Feasibility

This involves questions such as whether the firm can afford to build the system, whether its
benefits should substantially exceed its costs, and whether the project has higher priority than
other projects that might use the same resources.

Technical Feasibility

This involves questions such as whether the technology needed for the system exists, how difficult
it will be to build, and whether the firm has enough experience using that technology.

Schedule Feasibility

This involves questions such as how much time is available to build the new system, when it can be
built (i.e. during holidays), interference with normal business operation, etc.

Organizational Feasibility

This involves questions such as whether the system has enough support to be implemented
successfully, whether it brings an excessive amount of change, and whether the organization is
changing too rapidly to absorb it.
 2016
CD Management]

HARDWARE SPECIFICATION
 IBM Compatible PC with minimum Pentium-II 350Mhz Processor

 64 MB RAM

 2 GB Hard Disk Space

 CD Rom for installation of software

 Printer for Report Generation and Billing

SOFTWARE SPECIFICATION
 Microsoft Windows 98/Me/2000/XP/NT/Server 2003/Vista

 MS Access 97/2000/XP/2003/2007 (For Database Management)

 Microsoft Visual Basic (For Code Testing)

 2016
CD Management]

VISUAL BASIC

VB is an event driven programming language and associated development environment from

Microsoft. VB has been replaced byVisual Basic.NET. The older version of VB1 was derived heavily
from BASIC and enables rapid application development(RAD) of graphical user interface(GUI)
applications, access to database using DAO,RDO or ADO, and creation of ActiveX controls and
objects.

A programmer can put together an application using the components provided with Visual Basic
itself. Programs written in Visual Basic can also use theWindows API, but doing so requires external
function declarations.

The language not only allows programmers to easily create simple GUI applications, but also has
the flexibility to develop fairly complex applications as well. Programming in VB is a combination of
visually arranging components or controls on a form, specifying attributes and actions of those
components, and writing additional lines of code for more functionality. Since default attributes
and actions are defined for the components, a simple program can be created without the
programmer having to write many lines of code. Performance problems were experienced by
earlier versions, but with faster computers and native code compilation this has become less of an
issue.

Forms are created using drag and drop techniques. A tool is used to place controls (e.g., text boxes,
buttons, etc.) on the form (window). Controls have attributes and event handlers associated with
them. Default values are provided when the control is created, but may be changed by the
programmer. Many attribute values can be modified during run time based on user actions or
changes in the environment, providing a dynamic application. For example, code can be inserted
into the form resize event handler to reposition a control so that it remains centered on the form,
expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text
box, the program can automatically translate the case of the text being entered, or even prevent
certain characters from being inserted.
 2016
CD Management]
Visual Basic can create executables(EXE), ActiveX controls, DLL files, but is primarily used to develop
Windows applications and to interface web database systems. Dialog boxes with less functionality
(e.g., no maximize/minimize control) can be used to provide pop-up can insert additional logic

within the appropriate event handlers. For example, a drop-down combination box will
automatically display its list and allow the user to select any element.

An event handler is called when an item is selected, which can then execute additional code
created by the programmer to perform some action based on which element was selected, such as
populating a related list.

VISUAL BASIC FEATURE

Data access features allow you to create databases, front-end applications and scalable
server-side components for most popular database formats, including Microsoft SQL Server
and other enterprise-level databases.

ActiveX technologies allow you to use the functionality provided by other applications, such
as Microsoft Word, Word processor, Microsoft Excel Spreadsheet, and other windows
applications. You can even automate application and objects created using the Professional
or Enterprise edition of Visual Basic.

Internet capabilities make it easy to provide access to documents and applications across
the Internet or the Internet from within your application or to create Internet server
applications.

Your finished application is a true .exe file that uses a Visual Basic Virtual Machine that you
can freely distribute.

Visual Basic component can have no user interface, and instead provide ActiveX objects to
other programs via Component Object Model (COM). This allows for server-side processing
or an add-in module.

The language is garbage collected using reference counting, has a large library of utility
objects, and has basic object oriented support.

Visual Basic is generally not case sensitive, although it will transform keywords into a standard case
configuration and force the case of variable names to conform to the case of the entry within the
 2016
CD Management]
symbol table entry. String comparisons are case sensitive by default, but can be made case
insensitive if so desired.
 2016
CD Management]

INTRODUCTION TO MS ACCESS

Microsoft Access is a relational database management system from Microsoft, packaged with
Microsoft Office Professional which combines the relational Microsoft Jet Database Engine with a
graphical user interface. It can use data stored in Access/Jet, SQL Server, Oracle, or any ODBC-
compliant data container. Skilled software developers and data architects use it to develop
powerful, complex application software. Relatively unskilled programmers and non-programmer
“power users” can use it to build simple applications without having to deal with features they
don’t understand. It supports substantial object-oriented (OO) techniques but falls short of being a
fully OO development tool.

Compatibility with SQL – queries may be viewed and edited as SQL statements, and SQL
statements can be used directly in Macros and VBA Modules to manipulate Access tables.
Users may mix and use both VBA and “Macros” for programming forms and logic and offers
object-oriented possibilities.

Access’ cut and paste functionality can make it a useful tool for connecting between other
databases (for example, Oracle and Microsoft SQL Server during data or database
conversions).

Access comes with various import and export features that allow integration with Windows
and other platform applications, several of which can be executed on demand from within
applications or manually by the user.

The report writer in Access, while capable and up to the task of sophisticated report
creation.

Access to run stored procedures in RDBMSs that support these.

 2016
CD Management]

TESTING PROCESS
Software testing is the process used to help identify the correctness, completeness, security and
quality of developed computer software. With that in mind, testing can never completely establish
the correctness of arbitrary computer software. In computability theory, a field of computer
science, an elegant mathematical proof concludes that it is impossible to solve the halting problem,
the question of whether an arbitrary computer program will enter an infinite loop, or halt and
produce output.

There are many approaches to software testing

White-box testing

In white box testing the test developer has access to the source code and can write code that links
into the libraries which are linked into the target software. This is typical of unit tests, which only
test parts of a software system.

black-box testing

In black box testing the test engineer only accesses the software through the same interfaces that
the customer or user would, or possibly through remotely controllable, automation interfaces that
connect another computer or another process into the target of the test.

Gray-box testing

In recent years the term grey (or gray in the United States) box testing has come into common
usage. The typical grey box tester is permitted to set up or manipulate the testing environment, like
seeding a database, and can view the state of the product after their actions.

Regression Testing

A regression test re-runs previous tests against the changed software to ensure that the changes
made in the current software do not affect the functionality of the existing software. Regression
testing can be performed either by hand or by software that automates the process.
 2016
CD Management]

REQUIREMENT DETERMINATION TECHNIQUES

For obtaining the knowledge of existing system and expectations from proposed system
information is collected by using different tools such as :-

Interviews

Interviews were conducted with the patient of the hospital to collect the information. Their queries
regarding Computerization were answered. The flow of information was understood and the
drawbacks of the current Manual system were noted. Their Extra demand was also noted.
Interviews allowed me to discover areas of Misunderstanding, and expectation for the proposed
system.

Document Study

All the registers such as admission condition description and various files etc of the firm were
reviewed to determine the method of storage of the data. This process helped a great deal in
designing the files of the computerized system. The inputs of the manual system were noted. New
formats of output reports were designed to improve the clarity of the system.

Observation

The day-to-day working of the manual system was observed and the areas in which
computerization could be used most effectively. Fact-finding offered me, and Opportunity to go
Behind the scenes in a firm, to learn the inside story, to discover how things actually works in a new
area of information.
 2016
CD Management]

SPIRAL MODEL

Spiral model that couples the iterative nature of prototyping model with the well controlled and
disciplined aspects of the linear sequential model. It gives the capability for rapid development of
the software’s incremental versions.

A spiral model is broken into the following framework activities called

task regions-

Customer Communication – This is the task required to achieve effective communication between
a developer and a customer

Planning - This is for defining resources timelines and other project-related information

Risk Analysis - It is needed to assess both technical and management risks.

Engineering - These tasks are required to build one or more application representations.

Construction and Release - It is required to construct, test, install and give user support.

Customer Evaluation - This is to get customer feedback. It is based on the software representation
evaluation that are created during the engineering stage and used during the installation.

Planning Risk Analysis

Customer
Communication

Engineering

Customer Evaluation
 2016
CD Management]

Login Form
 2016
CD Management]
 2016
CD Management]

Company Details Entry

CD Details Entry Form

 2016
CD Management]

Purchase Order Details Entry Form

 2016
CD Management]

CD Received Form
 2016
CD Management]

CD Issued Form
 2016
CD Management]

Company Details Report

 2016
CD Management]

Purchase Order Details Form

Purchase Order Details Report

 2016
CD Management]

CD Receive Details Form

CD Receive Details Report

 2016
CD Management]

Quantity on Hand Report

 2016
CD Management]
BIBLIOGRAPHY

Mastering In Visual Basic 6.0 - Brian Siller

MS-Office-97 - Ginny Cuottor

Software Engineering - Pressman

Database Management System - C.J. Date

WEBLIOGRAPHY

www.wikipedia.org
www.google.com
 2016
CD Management]

Coding of Login Form

Private Sub Command1_Click()

If UCase(txtPassword.Text) = "EPS" And UCase(txtUserName.Text) = "EPS" Then
MDIForm1.Show
Unload Me
Else
MsgBox "Invalid Password or Username"
txtPassword.Text = ""
txtUserName.Text = ""
txtUserName.SetFocus
End If
End Sub

Private Sub Command2_Click()

End
End Sub
 2016
CD Management]

Coding of Main Form

Dim conn As New ADODB.Connection

Private Sub addcom_Click()

FRMCOMPANY.Show
End Sub

Private Sub addeq_Click()

frmCDMaster.Show
End Sub

Private Sub Cmp_Click()

Dim rs As New ADODB.Recordset
rs.Open "SELECT * FROM company_master", conn, 1, 3
With companymaster
Set .DataSource = rs
.Sections(3).Controls("cid").DataField = rs.Fields("company_id").Name
.Sections(3).Controls("cname").DataField = rs.Fields("name").Name
.Sections(3).Controls("address").DataField = rs.Fields("address").Name
.Sections(3).Controls("contact_no").DataField = rs.Fields("contact_no").Name
End With
companymaster.Show
End Sub

Private Sub eid_Click()

RptIssue.Show
End Sub

Private Sub erd_Click()

rptrecdetails.Show
End Sub

Private Sub ext_Click()

End
End Sub

Private Sub issuequ_Click()

FrmEquIssue.Show
End Sub

Private Sub MDIForm_Load()

If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
End Sub
 2016
CD Management]

Private Sub qoh_Click()

Dim rs1 As New ADODB.Recordset
Dim rs2 As New ADODB.Recordset
Dim rs3 As New ADODB.Recordset
Dim rs4 As New ADODB.Recordset
conn.Execute ("delete from temp")
rs1.Open "select ename,etype from CD_master", conn, 1, 3
Do Until rs1.EOF
rs2.Open "select sum(rec_qty) from CD_rec,po_master where CD_rec.po_no=po_master.po_no
and po_master.ename='" & rs1.Fields(0) & "' and po_master.etype='" & rs1.Fields(1) & "'", conn, 1,
3
rs3.Open "select sum(issue_qty) from CD_issue where ename='" & rs1.Fields(0) & "' and etype='"
& rs1.Fields(1) & "'", conn, 1, 3
If IsNull(rs2.Fields(0)) = True Then
recqty = 0
Else
recqty = Val(rs2.Fields(0))
End If
If IsNull(rs3.Fields(0)) = True Then
issueqty = 0
Else
issueqty = Val(rs3.Fields(0))
End If
bal = recqty - issueqty

conn.Execute ("Insert into temp values('" & rs1.Fields(0) & "','" & rs1.Fields(1) & "'," & Val(bal) &
")")
rs3.CLOSE
rs2.CLOSE
rs1.MoveNext
Loop
rs1.CLOSE

rs4.Open "select * from temp", conn, 1, 3

With qtyonhand
Set .DataSource = rs4
.Sections(3).Controls("ename").DataField = rs4.Fields("ename").Name
.Sections(3).Controls("etype").DataField = rs4.Fields("etype").Name
.Sections(3).Controls("qty").DataField = rs4.Fields("qty").Name

End With
qtyonhand.Show

End Sub

Private Sub recequ_Click()

frmEREC.Show
End Sub
 2016
CD Management]

Coding of CD Master

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset
Dim rs1 As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
Set rs1 = conn.Execute("SELECT COUNT(EID) FROM CD_MASTER")
eid.Text = rs1.Fields(0) + 1
FILLENAME
FILLCNAME
End Sub

Private Sub RATE_KeyPress(KeyAscii As Integer)

numcheck KeyAscii
End Sub

Private Sub SAVE_Click()

If ENAME.Text <> "" And CNAME.Text <> "" And ETYPE.Text <> "" And RATE.Text <> "" And
UNIT.Text <> "" Then
conn.Execute ("Insert into CD_MASTER values(" & Val(eid.Text) & ",'" & UCase(ENAME.Text)
& "','" & UCase(ETYPE.Text) & "'," & CNAME.ItemData(CNAME.ListIndex) & "," & Val(RATE.Text) &
",'" & UNIT.Text & "')")
eid.Text = ""
ENAME.Text = ""
ETYPE.Text = ""
CNAME.Text = ""
RATE.Text = ""
UNIT.Text = ""

Set rs1 = conn.Execute("SELECT COUNT(EID) FROM CD_MASTER")

eid.Text = rs1.Fields(0) + 1
ENAME.SetFocus
SAVE.Caption = "SAVE"
FILLCNAME
FILLENAME
Else
MsgBox "PLEASE FILL VALUES "
End If
 2016
CD Management]

Private Sub FILLENAME()

rs.Open "select * from CD_MASTER order by ENAME", conn, 1, 3
ENAME.Clear
Do Until rs.EOF
ENAME.AddItem (rs.Fields(1))
rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLCNAME()
rs.Open "select * from COMPANY_MASTER order by name", conn, 1, 3
CNAME.Clear
Do Until rs.EOF
CNAME.AddItem (rs.Fields(1))
rs.MoveNext
Loop
rs.CLOSE
End Sub
 2016
CD Management]

Coding of Purchase Order Generate

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset
Dim rs1 As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub ENAME_Click()

FILLETYPE
End Sub

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
Set rs1 = conn.Execute("SELECT COUNT(PO_NO) FROM PO_MASTER")
PONO.Text = rs1.Fields(0) + 1
PODATE.Value = Date
FILLENAME
FILLpo
End Sub
Private Sub FILLENAME()
rs.Open "select * from CD_MASTER order by ENAME", conn, 1, 3
ENAME.Clear
Do Until rs.EOF
ENAME.AddItem (rs.Fields(1))
rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLpo()
rs.Open "select * from po_MASTER order by po_no", conn, 1, 3
POLIST.Clear
Do Until rs.EOF
POLIST.AddItem (rs.Fields(0))
rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLETYPE()
rs.Open "select * from CD_MASTER WHERE ENAME='" & ENAME.Text & "'", conn, 1, 3
ETYPE.Clear
Do Until rs.EOF
ETYPE.AddItem (rs.Fields(2))
 2016
CD Management]
rs.MoveNext
Loop
rs.CLOSE
End Sub

Private Sub POLIST_Click()

On Error Resume Next
SAVE.Caption = "UPDATE"
rs.Open "SELECT * FROM PO_MASTER WHERE po_no=" & Val(POLIST.Text), conn, 1, 3
If rs.EOF = False Then
PONO.Text = rs.Fields(0)
PODATE.Value = rs.Fields(1)
ENAME.Text = rs.Fields(2)
ETYPE.Text = rs.Fields(3)
QTY.Text = rs.Fields(4)
RATE.Text = rs.Fields(5)
ISSUE.Text = rs.Fields(6)
SUPPLIER.Text = rs.Fields(7)
End If
rs.CLOSE
End Sub

Private Sub QTY_Change()

amount.Text = Val(QTY.Text) * Val(RATE.Text)
End Sub

Private Sub QTY_KeyPress(KeyAscii As Integer)

numcheck KeyAscii
End Sub

Private Sub RATE_Change()

amount.Text = Val(QTY.Text) * Val(RATE.Text)
End Sub

Private Sub RATE_KeyPress(KeyAscii As Integer)

numcheck KeyAscii
End Sub

Private Sub SAVE_Click()

If ENAME.Text <> "" And ETYPE.Text <> "" And QTY.Text <> "" And RATE.Text <> "" Then
If SAVE.Caption = "SAVE" Then
conn.Execute ("Insert into PO_MASTER values(" & Val(PONO.Text) & ",'" & PODATE.Value &
"','" & UCase(ENAME.Text) & "','" & ETYPE.Text & "'," & Val(QTY.Text) & "," & Val(RATE.Text) & ",'"
& ISSUE.Text & "','" & SUPPLIER.Text & "')")
Else
conn.Execute ("UPDATE PO_MASTER SET ENAME='" & UCase(ENAME.Text) & "',ETYPE='" &
UCase(ETYPE.Text) & "',ORDER_QTY=" & Val(QTY.Text) & ",RATE=" & Val(RATE.Text) &
",ISSUEDBY='" & UCase(ISSUE.Text) & "',SUPPLIER='" & UCase(SUPPLIER.Text) & "' WHERE PO_NO="
& Val(PONO.Text))
End If
 2016
CD Management]

PONO.Text = ""
PODATE.Value = Date
ENAME.Text = ""
ETYPE.Text = ""
QTY.Text = ""
RATE.Text = ""
ISSUE.Text = ""
SUPPLIER.Text = "-"
Set rs1 = conn.Execute("SELECT COUNT(PO_NO) FROM PO_MASTER")
PONO.Text = rs1.Fields(0) + 1
FILLENAME
FILLpo
ENAME.SetFocus
SAVE.Caption = "SAVE"
Else
MsgBox "PLEASE FILL VALUES "
End If
End Sub
 2016
CD Management]

Coding of CD Receive

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset
Dim rs1 As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub Command1_Click()

On Error Resume Next
rs.Open "SELECT * FROM PO_MASTER WHERE po_no=" & Val(PONO.Text), conn, 1, 3
If rs.EOF = False Then
'PONO.Text = rs.Fields(0)
PODATE.Value = rs.Fields(1)
ENAME.Text = rs.Fields(2)
ETYPE.Text = rs.Fields(3)
QTY.Text = rs.Fields(4)
RATE.Text = rs.Fields(5)
ISSUE.Text = rs.Fields(6)
SUPPLIER.Text = rs.Fields(7)
rs1.Open "select sum(rec_qty) from CD_rec where po_no=" & Val(PONO.Text), conn, 1, 3
If rs.EOF = False Then
If IsNull(received.Text) = True Then
received.Text = 0
Else
received.Text = Val(rs1.Fields(0))
End If
End If
rs1.CLOSE
recqty.SetFocus

Else
MsgBox "Check Purchase Order No. "
PONO.Text = ""
PODATE.Value = Date
ENAME.Text = ""
ETYPE.Text = ""
QTY.Text = ""
RATE.Text = ""
ISSUE.Text = ""
SUPPLIER.Text = ""
PONO.SetFocus
received.Text = ""
End If
rs.CLOSE
End Sub
 2016
CD Management]

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
recdate.Value = Date
End Sub

Private Sub RATE_Change()

amount.Text = Val(QTY.Text) * Val(RATE.Text)
End Sub

Private Sub recqty_Change()

balqty.Text = Val(QTY.Text) - (Val(recqty.Text) + Val(received.Text))
If Val(balqty.Text) < 0 Then
MsgBox "Check Rec Qty"
recqty.Text = ""
balqty.Text = ""
recqty.SetFocus
End If
End Sub

Private Sub recqty_KeyPress(KeyAscii As Integer)

numcheck KeyAscii
End Sub

Private Sub SAVE_Click()

If recqty.Text <> "" Then
conn.Execute ("insert into CD_rec values(" & Val(PONO.Text) & ",'" & recdate.Value & "'," &
Val(recqty.Text) & ",'" & remark.Text & "')")
MsgBox "Saved"
PONO.Text = ""
PODATE.Value = Date
ENAME.Text = ""
ETYPE.Text = ""
QTY.Text = ""
RATE.Text = ""
ISSUE.Text = ""
SUPPLIER.Text = ""
recdate.Value = Date
recqty.Text = ""
balqty.Text = ""
remark.Text = "-"
PONO.SetFocus
Else
MsgBox "Fill Rec Qty"
End If
End Sub
 2016
CD Management]

Coding of CD Issue

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset
Dim rs1 As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub ENAME_Click()

FILLETYPE
End Sub

Private Sub ETYPE_Click()

Dim R As Integer
Dim I As Integer
Set rs1 = conn.Execute("SELECT sum(rec_qty) FROM CD_rec where PO_No in(select PO_NO from
PO_Master where ename='" & ENAME.Text & "' and etype='" & ETYPE.Text & "')")
If IsNull(rs1.Fields(0)) = True Then
R=0
Else
R = rs1.Fields(0)
End If
Set rs1 = conn.Execute("SELECT sum(Issue_qty) FROM CD_Issue where ename='" & ENAME.Text &
"' and etype='" & ETYPE.Text & "'")
If IsNull(rs1.Fields(0)) = True Then
I=0
Else
I = rs1.Fields(0)
End If
avi.Text = R - I
End Sub

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
IssueDAte.Value = Date
FILLENAME
End Sub
Private Sub FILLENAME()
rs.Open "select * from CD_MASTER order by ENAME", conn, 1, 3
ENAME.Clear
Do Until rs.EOF
ENAME.AddItem (rs.Fields(1))
 2016
CD Management]

rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLETYPE()
rs.Open "select * from CD_MASTER WHERE ENAME='" & ENAME.Text & "'", conn, 1, 3
ETYPE.Clear
Do Until rs.EOF
ETYPE.AddItem (rs.Fields(2))
rs.MoveNext
Loop
rs.CLOSE
End Sub

Private Sub issueqty_Change()

If Val(issueqty.Text) > Val(avi.Text) Then
MsgBox "Qty Not Available"
issueqty.Text = ""
issueqty.SetFocus
End If
End Sub

Private Sub issueqty_KeyPress(KeyAscii As Integer)

numcheck KeyAscii
End Sub

Private Sub SAVE_Click()

If issueqty.Text <> "" Then
conn.Execute ("insert into CD_issue values('" & ENAME.Text & "','" & ETYPE.Text & "','" &
IssueDAte.Value & "'," & Val(issueqty.Text) & ",'" & remark.Text & "')")
MsgBox "Issued"

IssueDAte.Value = Date
ENAME.Text = ""
ETYPE.Text = ""
issueqty.Text = ""
avi.Text = ""
remark.Text = "-"
Else
MsgBox "Fill Rec Qty"
End If
End Sub
 2016
CD Management]

Coding of CD Issue Report

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub Command1_Click()

Dim rs As New ADODB.Recordset
If Option1.Value = True Then
sql = "where ename='" & ENAME.Text & "' and etype='" & ETYPE.Text & "'"
'sql = " from CD_rec where po_no in(select po_no from po_master where ename='" &
ENAME.Text & "' and etype='" & ETYPE.Text & "')"
abc = ""
Else
sql = "where issue_date between #" & PODATE1.Value & "# and #" & podate2.Value & "#"
abc = Format(PODATE1.Value, "dd/MMM/yy") & " to " & Format(podate2.Value, "dd/MMM/yy")
End If
rs.Open "select * from CD_issue " & sql, conn, 1, 3
With ISSUE
Set .DataSource = rs
.Sections(2).Controls("l1").Caption = abc

.Sections(3).Controls("ename").DataField = rs.Fields("ename").Name
.Sections(3).Controls("etype").DataField = rs.Fields("etype").Name
.Sections(3).Controls("issue_date").DataField = rs.Fields("issue_date").Name
.Sections(3).Controls("issue_qty").DataField = rs.Fields("issue_qty").Name
.Sections(3).Controls("remark").DataField = rs.Fields("remark").Name
End With
ISSUE.Show
End Sub

Private Sub Form_Load()

PODATE1.Value = Date
podate2.Value = Date

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
FILLENAME
End Sub

Private Sub Option1_Click()

ENAME.Text = ""
 2016
CD Management]
ETYPE.Text = ""
ENAME.SetFocus
End Sub
Private Sub ENAME_Click()
FILLETYPE
End Sub
Private Sub FILLENAME()
rs.Open "select * from CD_MASTER order by ENAME", conn, 1, 3
ENAME.Clear
Do Until rs.EOF
ENAME.AddItem (rs.Fields(1))
rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLETYPE()
rs.Open "select * from CD_MASTER WHERE ENAME='" & ENAME.Text & "'", conn, 1, 3
ETYPE.Clear
Do Until rs.EOF
ETYPE.AddItem (rs.Fields(2))
rs.MoveNext
Loop
rs.CLOSE
End Sub
 2016
CD Management]

Coding of Purchase Order Report

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub Command1_Click()

Dim rs As New ADODB.Recordset
If Option1.Value = True Then
sql = "po_no=" & Val(PONO.Text)
abc = ""
Else
sql = "po_date between #" & PODATE1.Value & "# and #" & podate2.Value & "# order by po_no"
abc = Format(PODATE1.Value, "dd/MMM/yy") & " to " & Format(podate2.Value, "dd/MMM/yy")
End If
rs.Open "SELECT * FROM po_master where " & sql, conn, 1, 3
With podetails
Set .DataSource = rs
.Sections(2).Controls("l1").Caption = abc
.Sections(3).Controls("po_no").DataField = rs.Fields("po_no").Name
.Sections(3).Controls("po_date").DataField = rs.Fields("po_date").Name
.Sections(3).Controls("ename").DataField = rs.Fields("ename").Name
.Sections(3).Controls("etype").DataField = rs.Fields("etype").Name
.Sections(3).Controls("order_qty").DataField = rs.Fields("order_qty").Name
.Sections(3).Controls("rate").DataField = rs.Fields("rate").Name
.Sections(3).Controls("issuedby").DataField = rs.Fields("issuedby").Name
.Sections(3).Controls("supplier").DataField = rs.Fields("supplier").Name

End With
podetails.Show
End Sub

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
PODATE1.Value = Date
podate2.Value = Date

End Sub
 2016
CD Management]

Coding of CD Received Report

Dim conn As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub CLOSE_Click()

Unload Me
End Sub

Private Sub Command1_Click()

Dim rs As New ADODB.Recordset
If Option1.Value = True Then
sql = " rec_date,rec_qty,remark,po_master.ename as ename,po_master.etype as etype from
CD_rec,po_master where CD_rec.po_no=po_master.po_no and po_master.ename='" &
ENAME.Text & "' and po_master.etype='" & ETYPE.Text & "'"
'sql = " from CD_rec where po_no in(select po_no from po_master where ename='" &
ENAME.Text & "' and etype='" & ETYPE.Text & "')"
abc = ""
Else
sql = " rec_date,rec_qty,remark,po_master.ename as ename,po_master.etype as etype from
CD_rec,po_master where CD_rec.po_no=po_master.po_no and CD_rec.rec_date between #" &
PODATE1.Value & "# and #" & podate2.Value & "#"
abc = Format(PODATE1.Value, "dd/MMM/yy") & " to " & Format(podate2.Value, "dd/MMM/yy")
End If
rs.Open "select " & sql, conn, 1, 3
With rec
Set .DataSource = rs
.Sections(2).Controls("l1").Caption = abc
.Sections(3).Controls("rec_date").DataField = rs.Fields("rec_date").Name
.Sections(3).Controls("ename").DataField = rs.Fields("ename").Name
.Sections(3).Controls("etype").DataField = rs.Fields("etype").Name
.Sections(3).Controls("rec_qty").DataField = rs.Fields("rec_qty").Name
.Sections(3).Controls("remark").DataField = rs.Fields("remark").Name
End With
rec.Show
End Sub

Private Sub Form_Load()

center Me
If conn.State = 1 Then conn.CLOSE
conn.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & App.Path & "\EPS.mdb;Persist
Security Info=False"
FILLENAME
PODATE1.Value = Date
podate2.Value = Date

End Sub
 2016
CD Management]
Private Sub Option1_Click()
ENAME.Text = ""
ETYPE.Text = ""
ENAME.SetFocus
End Sub
Private Sub ENAME_Click()
FILLETYPE
End Sub
Private Sub FILLENAME()
rs.Open "select * from CD_MASTER order by ENAME", conn, 1, 3
ENAME.Clear
Do Until rs.EOF
ENAME.AddItem (rs.Fields(1))
rs.MoveNext
Loop
rs.CLOSE
End Sub
Private Sub FILLETYPE()
rs.Open "select * from CD_MASTER WHERE ENAME='" & ENAME.Text & "'", conn, 1, 3
ETYPE.Clear
Do Until rs.EOF
ETYPE.AddItem (rs.Fields(2))
rs.MoveNext
Loop
rs.CLOSE
End Sub
 2016
CD Management]

Coding of Module

Sub center(frm As Form)

If frm.WindowState = vbNormal Then
frm.Move (MDIForm1.ScaleWidth - frm.Width) / 2, (MDIForm1.ScaleHeight - frm.Height) / 2
End If
End Sub

Public Sub numcheck(KeyAscii As Integer)

If Not ((KeyAscii >= 48 And KeyAscii <= 57) Or KeyAscii = 46 Or KeyAscii = 8 Or KeyAscii = 13) Then
MsgBox "Please Enter Only Numbers(0-9)"
KeyAscii = 7
End If
End Sub