ON

DATA ENTRY SYSTEM OF INTERNATIONAL GARRAGE

Submitted to:
SIKKIM MANIPAL UNIVERSITY For the partial fulfillment of the Award of Degree of
BACHELOR OF COMPUTER APPLICATIONS

Developed By: Under the guidance of: Rahul Raina Priya Raina Reg. No. 520931678

CERTIFICATE

It

is to certify that Rahul Raina , Registration No. 520931678

has

completed the project work, Data Entry System of International Garrage for the partial fulfillment of the award of the degree of BACHELOR OF COMPUTER APPLICATIONS by Sikkim Manipal University.

Sig. of Project Guide

ACKNOWLEDGEMENT
Lots of work, a lot of people and a lot of understanding goes into writing any report and this one is no difference. I would like to take this opportunity to thank all of those who have helped me see through the very end of this project. I express my deep and sincere gratitude to the Respected Principal who provided me the opportunity, inspiration and requisite facility and giving me the chance to show the capabilities in this esteemed Institution. My teachers kind and elderly advice has always inspired me to put in all my efforts to develop this project. In this regard, I would like to pay my sincere thanks to all the teachers for providing me continuous invaluable guidance throughout the project inspite of their busy schedule. Last but not the least; I am very grateful to my parents for their loving support and encouragement, which has helped me to reach this stage. Above all my thanks are also due to the Almighty God. So I leave this acknowledgement to in their reminiscence

RAHUL RAINA

TABLE OF CONTENTS
Profile System Development Life Cycle
System Analysis System Design Design Concepts Design Objectives Design Modules Architectural Design Context Analysis Diagram Data Flow Diagrams Detailed Design Application Design Problem Definition Drawbacks of the Existing System Proposed System Significance of the Proposed System Advantages of the Proposed System Requirement Analysis Feasibility Study

Coding Screen Shots Bibliography

INTRODUCTION

Project on Data Entry System International National Garrages is developed by a Rahul Raina for providing fully computerized system of International National Garrage to users. With the help of this project, we are making efforts to fully computerize the systems of National Garrage providing Vechial different services to the customers by like

particular, payment particular, finance and

receipts. By this way, we can help the user to get the exact information and services used by the customers at a glance and lengthy manual work can be avoided and there is no need to maintain a register for keeping all the records about customers. So, there is a saving of time & money and by this way, efficiency of the management improved. of National Garrage System can be

PROJECT PROFILE Project Title Supervisor Technical Specification Hardware Environment Data Entry System of International Garrage Rahul Raina

Processor RAM HARD DISK

Pentium-IV 1 MB RAM 160 GB

Software Environment OPERATING SYSTEM SERVICE PACK 2 BACK END FRONTEND ACCESS MICROSOFT VISUAL BASIC

Submitted to:

Sikkim Manipal University

System development Life Cycle

System Development revolves around a life cycle that begins with the recognition of user needs. In order to develop good software, it has to go through different phases. There are various phases of the System Life Cycle of this project. There are different models for software development, which depict these phases. We decided to use waterfall model, the oldest and the most widely used paradigm for software engineering. The Various relevant stages of the System Life Cycle of this Application Tool are depicted in the following flow diagram .

SYSTEM ANAYLSIS

SYSTEM DESIGN

CODING

SYSTEM TESTING

SYSTEM IMPLEMENTATION

SYSTEM MAINTENANCE

Let us have a look on each of the above activities:

1. System Analysis
System Analysis is the process of diagnosing situations, done with a defiant aim, with the boundaries of the system kept in mind to produce a report based on the findings. Analysis is fact-finding techniques where problem definition, objective, system requirement specifications, feasibility analysis and cost benefit analysis are carried out. The requirement of both the system and the software are document and reviewed with the user.

2. System Design
System Design is actually a multistep process that focuses on four distinct attributes of a program: data structures, software architecture, interface representations, and procedural (algorithmic) detail. System design is concerned with identifying the software components (Functions, data streams, and data stores), specifying relationships among components, specifying software structure, maintaining a record of design decisions and providing a blueprint for the implementation phase.

3. Coding
Coding step performs the translations of the design representations into an artificial language resulting in instructions that can be executed by the computer. It thus involves developing computer programs that meet the system specifications of design stage.

4. System Testing
System testing process focuses on the logical internals of the software, ensuring that all statements have been tested on the functional externals, that is conducting tests using various tests data

to uncover errors that defined input will produce actual results that agree with required results. The basic idea of software development life cycle (SDLC) is that there is as well defined process by which an application is conceived, developed and implemented. The phases in the SDLC provide a basis for the management and control because they define segments of the flow of work, which can be identified for the managerial purpose and specifies the documents or other deliveries to be produced in each phase.

1. System Implementation
System Implementation is a process that includes all those activities that take place to convert an old system to a new system. The new system may be totally new system replacing the existing system or it may be major modification to the existing system. Coding performs the translations of the design representations into an artificial language resulting in instructions that can be executed by the computer. It thus involves developing computer programs that meet the system design specifications. System implementation involves the translation of the design specifications into source code and debugging, documentation and unit testing of the source code.

SYSTEM ANAYLSIS

10

Problem Definition
Information systems are sophisticated data management tools and powerful user interfaces integrated into conventional data centres. These information systems offer a flexible and fast access to the ever increasing amount of data. To create and operate information systems, special knowledge about storage of data is necessary. Our proposal for a Horticulture Management Information System is based on the concept for integrated information systems. All users will have the same convenient access on desired data using easy to handle data retrieving and exchange data transfer tools linked to a graphic user interface (GUI). All received data will be checked for plausibility, integrity and format compatibility, to create harmonized and complete databases and exchange data sets. The data access protection is realized by user and password dependent system rights. A high degree of data disposal will be achieved using an up-to date relational database management system (RDBMS)

Objective of the project

The main objective of making this project is to fully automate the Horticulture Managment System. The prime reason for automating the manual management process of the company is to facilitate the management personnel by keeping the data and information in a wellordered manner in the data store. By having the computerized system, queries can be quickly and easily entertained and top level personnel of the organization can make future decisions by analyzing information generated in the form of reports.

11

Demerits of Existing System

Delay in flow of information from grass root level in absence of constant touch Generation of data is attempted manually. Many hands involved Papers, files and folders are needed. Space for storage like Almirahs & Boxes etc needed. Fax paper, Zerox machines - paper addition - again more bundles of packs. Using of computers for repetitive typing for same work Difficult rather unmanageable to monitor the functioning of departments. No standarisation, repetition of same work at different times

Merits of Proposed system

Performance is watched daily. Hence constant touch. No need to work for generation of data & information. The system exhibits instantaneously with a click. No such need arises. No storage required. It is managed in the web space. Paperless data stored and retrieved Computers are simply means to exhibit already stored data Extremely easy to monitor daily performance. Once fed retrieved at will even for minutest details.

12

FEASIBILITY STUDY
The feasibility study is carried out to test if the proposed system is worth being implemented. Given unlimited and infinite time, all projects are feasible. Unfortunately such resources and time are not possible in real life situations. Hence it becomes both necessary and prudent to evaluate the feasibility of the project at the earliest possible time in order to avoid unnecessarily wastage of time, effort and professional embarrassment over an ill conceived system. Feasibility study is a test of system proposed regarding its work ability, impact on the organization ability to meet the user needs and effective use of resources. The main objective of feasibility study is to test the technical, operational and economical feasibility of developing a computer system Application. The following feasibility studies were carried out for the proposed system: Economic Feasibility: An evaluation of development cost weighed against the income of benefit derived from the developed system. Here the development cost is evaluated by weighing it against the ultimate benefits derived from the new system. The proposed system is economically feasible if the benefits obtained in the long run compensate rather than overdo the cost incurred in designing and implementing. In this case the benefits outweigh the cost that makes the system economically feasible. Technical Feasibility: A study of function performance and constraints that may affect the ability to achieve the acceptable system. A system is technically feasible, if it can be designed and implemented within the limitations of available resources like funds, hardware, software etc. The considerations that are normally associated with technical feasibility include 13

development

risk,

resources

availability

and

technology.

Management provides latest hardware and software facilities for successful completion of the project. The proposed system is technically feasible as the existing staff can be trained to operate the computerized system and costs involved are reasonable considering the benefits and the future aspects. The software developed is reliable and provides user with ease of success. Operational Feasibility: Proposed System is beneficial only if it can be turned into information system that meets the organizations operating requirements. The development of the new system was started because of the requirements put forward by the management of the concerned department. So it is sure that the system developed is operationally feasible. The availability of the required hardware, system software and technical manpower makes the system operationally feasible. Behavioral Feasibility: An evaluation of the behavior of the end users, which may effect the development of the system. The user show minimal resistance to change, but they are satisfied with functionality provided in the proposed system. Motivational Feasibility: Evaluation of organization

motivation to support the development and implementation of project. Organizational motivation was always there through out the project. Schedule Feasibility: Evaluates the time taken in the development of the project. The system had schedule feasibility.

14

SYSTEM DESIGN

15

DESIGN CONCEPTS
The design of an information system produces the detail that state how a system will meet the requirements identified during system analysis. System specialists often refer to this stage as Logical Design, in contrast to the process of development program software, which is referred to as Physical Design. System Analysis begins process by identifying the reports and the other outputs the system will produce. Then the specific on each are pin pointed. Usually, designers sketch the form or display as they expect it to appear when the system is complete. This may be done on a paper or computer display, using one of the automated system tools available. The system design also describes the data to be input, calculated or stored. Individual data items and calculation procedures are written in detail. The procedure tells how to process the data and produce the output.

DESIGN OBJECTIVES
The following goals were kept in mind while designing the system: To reduce the manual work required to be done in the existing system. To avoid errors inherent in the manual working and hence make the outputs consistent and correct. To improve the management of permanent information of the Department by keeping it in properly structured tables and to provide facilities to update this information efficiently as possible. To make the system completely menu-driven and hence user friendly, and hence user friendly, this was necessary so that even non-programmers could use the system efficiently. To make the system completely compatible i.e., it should fit in the total integrated system. 16

To design the system in such a way that reduced future maintenance and enhancement times and efforts. To make the system reliable, understandable and cost effective.

DESIGN MODULES
The software has been designed in a modular manner. There is a separate module for the every function of the Management System. These are then integrated to build an easy to use system. Here is a brief listing of the various Design Modules of the Software: 1. Login 2. Horticulture Management Information system 3. Generation of the Search Results. 4. Generation of the Reports.

SYSTEM DESIGN
The design stage takes the final specification of the system from analysis stages and finds the best way of filing them, given the technical environment and previous decision on required level of automation. The system design is carried out in two phases: i) ii) Architectural Design (High Level Design) Detailed Design (Low Level Design)

ARCHITECTURAL DESIGN
The high level Design maps the given system to logical data structure. Architectural design involves identifying the software component, decoupling and decomposing the system into processing modules and conceptual data structures and specifying the

17

interconnection among components. Good notation can clarify the interrelationship and interactions if interest, while poor notation can complete and interfere with good design practice. A data floworiented approach was used to design the project. This includes Entity Relationship Diagram (ERD) and Data Flow Diagrams (DFD). Entity Relationship Diagram

One of the best design approaches is Entity Relationship Method. This design approach is widely followed in designing projects normally known as Entity Relationship Diagram (ERD). ERD helps in capturing the business rules governing the data relationships of the system and is a conventional aid for communicating with the end users in the conceptual design phase. ERD consists of: Entity It is the term use to describe any object, place, person, concept, activity that the enterprise recognizes in the area under investigation and wishes to collect and store data. It is diagrammatically represented as boxes. Attribute They are the data elements that are used to describe the properties that distinguish the entities. Relationship It is an association or connection between two or more entities. They are diagrammatically represented as arrows. A Unary relationship is a relationship between instances of the same entity. A Binary relationship is a relationship between two entities. A N-ary relationship is a relationship among N entities. It is defined only when the relationship does have a meaning without the participation of all the N entities.

18

 Degree of Relationship An important aspect of relationship between two or more entities is the degree of relationship. The different relationships recognized among various data stores in the database are: One-to-One (1:1) It is an association between two entities. For example, each student can have only one Roll No. One-to-Many (1:M) It describes entities that may have one or more entities related to it. For example, a father may have one or many children. Many-to-Many (M:M) It describes entities that may have relationships in both directions. This relationship can be explained by considering items sold by Vendors. A vendor can sell many items and many vendors can sell each item. ERD representation of the project is given below. It follows Chens convention in which entities are represented as rectangles and relationships as diamonds.

19

Analysis Diagram Context Analysis Diagram (CAD) is the top-level data flow diagram, which depicts the overview of the entire system. The major external entities, a single process and the output data stores constitute the CAD. Though this diagram does not depict the system in detail, it presents the overall inputs, process and the output of the entire system at a very high level. The Context Analysis Diagram if the project is given ahead. Data Flow Diagrams

A Data Flow Diagram (DFD) is a graphical tool used to describe and analyze the movement of data through a system manual or automated including the processes, stores of data and delays in the system. They are central tools and the basis from which other components are developed. It depicts the transformation of data from input to output through processes and the interaction between processes. Transformation of data from input to output through processes logically and independent of physical components is called the DFD. The physical DFD shows the actual implementation and movement of data between people, departments and workstation. DFDs are an excellent mechanism of communicating with the customers during requirement analysis and are widely used for representing external and top-level internal design specification. In the Later situations, DFDs are quite valuable for establishing naming conventions and names of system components such as subsystems, files and data links. In a DFD there are four components:

20

Sources or Destinations of data such as human, entities that interact with system, outside the system boundary, who form the source and the recipient of information are depicted in the form of a closed rectangle.

Data flow is a packet of data. It identifies data flow. It is a pipeline through which information flows. It is depicted in DFD as an arrow with the pointer pointing in the direction of flow. This connecting symbol connects an entity, process and data stores. This arrow mark also specifies the sender and the receiver.

Process depicts procedure, function or module that transforms input data into output data. It is represented as a circle or a bubble with the procedure name and a unique number inside the circle.

Data stores are the physical areas in the computers hard disk where a group of related data is stored in the form of files. They are depicted as an open-ended rectangle. The Data store is used either for storing data into the files or for reference purpose.

The DFD methodology is quite effective, especially when the required design is unclear. The DFD is easy to understand after a brief orientation.

21

DETAILED DESIGN
The Low Level Design maps the logical model of the system to a physical database design. Tables created for the system Entities and Attributes were mapped into Physical tables. The name of the entity is taken as the table name. During detailed design phase, the database if any and programming modules are designed and detailed user procedures are documented. The interfaces between the System users and computers are also defined.

APPLICATION DESIGN
After the detailed problem definition and system analysis of the problem, it was thought of designing web based Computer designing. Simplicity is hard to design. It is difficult to design something that is technically sophisticated but appears simple to use. Any software product must be efficient, fast and functional but more important it must be user friendly, easy to learn and use. For designing good interface we should use the following principles. i) ii) iii) iv) Clarity and consistency Visual feedback. Understanding the people. Good response.

Description of Modules: The Project consists of Four major modules: -

(i) User Validation module (ii) Entry module. (iii) Search Module. (iv) Report generation module
22

(i) User Validation Module:

Every user has to first interact with this User Validation Module. This module checks the authentication of a person and accordingly either invokes the report-generating module or data entry module. It interacts with the database to log in valid users. It includes options to change username or password.

(ii) Entry Module:

The main purpose of this module is to Store records of Area and production of Fresh/Dry fruits, accounts of plants in Nursery, Subsidy on tools, Health cover and court cases etc. The function of this module is to store data for queries regarding general information about the Area and Production of Fresh and Dry Fruits, Accounts of Plants in Nurseries, Subsidy on tools, Health Cover and Court Cases. This module will be at the top level and will be responsible for providing information to the management regarding various activities going on in the Department according to the query by the Administration.

(iii) Searching module:

This module is an important part of the project. This helps provide instant help to the Administration.

(iv) Report generation module:

This module is invoked by authentication checking module and it interacts with the database for extracting information on users request and accordingly generates reports.

23

PROPOSED SYSTEM
The form will be designed to collect one information from one applicant who is applying for loan. The user has to fill the information click on continue button if customer applying for loan is aged more then 60yrs then massage box will be displayed Sorry not eligible so person aged more then 60yrs is not allowed and the program end there. If customer age is less then 60yrs then the information related to property will be collected such as the cost of property, loan requirement, eligibility term (Which will be max. 15yrs for repayment or data of retirement which ever is earlier). After that information related to guarantor will be collected here. If guarantor salary is less then 5000 then message will be displayed that guarantor is not eligible. If eligible then message will be displayed for user informing them to click on calculates to find out customers eligibility. After that information will be displayed for the person applying for loan. Then information will contain name of person, man eligible amount (80% of total cost), and repayment term monthly EMI on eligibility, EMI factor per month.

24

SYSTEM IMPLEMENTATION

SYSTEM IMPLEMENTATION
The implementation is the final stage of the development. Implementation is the process of having system personnel check out

25

and put new equipment into use, train users, install the new application and construct any file of data needed to use it. Depending on the size of the organization that will be involved in using the application and the risk associated with its user, system developers may choose to pilot the operations in only one area of the firm, say in one department or with only one or two persons. Regardless of the implementation strategy used, developers strive to ensure that the systems initial use in trouble. Once installed, applications are often used for many years. However, both the organization and the user would change and the environment would be different over weeks and months. Therefore the application will undoubtedly have to be maintained, modifications and changes will be made to software, files or procedures to meet the emerging user requirements. In the sense, implementation is an ongoing process. This involves tasks like backing of the existing system data conversion and producing user documentation, user training, software distribution and set up of the infrastructure for the support of the new system. To implement the system, we must get the approval first. Then training program is conducted to give the demonstration of the system to the users. EDUCATION AND TRAINING Training the users is also important so that they can work with it without getting any problem; it is developer organization's duty to familiarize the users with the new system. User manuals are required for the users with the description of application flow charts. The screens should be shown to the users for teaching. Only authorized persons should be allowed to open the application.

26

USER INTERFACE In this section I have reproduced all the screens, which have been developed by me. Although, it was not possible to reproduce all the intermediate processing screens which user encounter while doing his job I have tried to put forth at least the major ones.

SYSTEM SECURITY System security is an essential part of the increased scale of computerization. So it is essential to keep enough security and privacy of the system so that neither physically nor operationally disturbed

BACK UP Back ups for the hardware, data and the system is inevitable factor to consider. Data back up represents insurance against actual loss of data due to equipment malfunction, application failure or accident, hence backup for the data must be provided on hard disk or on floppy disks.

27

SYSTEM TESTING

28

SYSTEM TESTING
System Testing is a vital part of software development life cycle. During the development of software, applications are written without the knowledge track of entire data. It is only during testing that we come to know about applications limitation and bugs. New systems must be thoroughly tested before being accepted. System testing implies testing programs/modules and their interaction. System testing is one of the most- crucial elements to which the attention is needed for the careful examination of the operations. System testing ensures the quality of the product and represents the ultimate review of specification, design and coding. Testing represents an interesting analogy for the System. During definition and development pleases, it was attempted to build software from an extract concept to tangible implementation. Testing phase is responsible for the assurance of good quality of the product. The system is tested successfully with the different testing technique. During system testing, the system is used experimentally to ensure that the software doesn't fail i.e. it will run according to its specification and in this way user expect. Special test data are input for processing, and the results examined. A limited number of users may be allowed to use the system so analysts can see whether they try to use it in unforeseen ways. It is preferable to discover any surprise before the organization implements the system and depends on it. In many organizations, testing is performed by the person other than those who wrote the original program to ensure more complete and unbiased testing and more reliable software. Since the users are not familiar to the new system, the data screen was designed in such a way that they were:

29

Consistent Easy to use Had a fast response time

The Following conventions were used while designing the various screens: All data related to one task is on a single screen. The user need not remember data from one screen to the next. All items that are logically related are together and arrange in importance from the top to bottom. Possible list values are provided to display all valid option to user. Error and Validation messages are provided wherever required.

TESTING PROCEDURE
Extensive Testing Procedures were followed, which included following: UNIT TESTING

At the very lowest level is unit testing, where the Programmer that writes the code, tests the code as per the specification of the Project. It tests the internal structure of the modules integrated in the application. All the checks and other constraints are tested and approved for further testing of application. All the modules are tested individually. Unit testing focuses verification effort on the smallest unit of software design the module. Using the detail design model as a guide, important control paths are used tested to uncover errors within the boundary of the module. The relative complexity of tests and the errors within the boundary of the module. The relative complexity of tests and the errors therein is limited by the constrained scope

30

established for unit testing. The unit test is always white-box oriented, and the step can be conducted in parallel for multiple modules. After a form has been created, the developer of the form fills out a unit test specification (UTS) document. This document contains all possible test conditions and their expected results. The module leader to ensure that no test condition has been neglected in the UTS then reviews this document. The features to be tested during Unit Testing are as follows 1. Each form must meet the functionality as specified in the system requirement specification. 2. In general, testing of a screen should include the following: 3. User Proper and logical navigation. Database field lengths consistent with the Proper format masks applied to fields. Correct computation (if applicable) as per the Boundary of non-database objects (fields, Correctness of database updates (if

corresponding table columns.

functionality. buttons etc) applicable) Query results(as per the input specified by interface(e.g. alignment of GUI objects, the user or any other criterion) appearance , title off screen, GUI object properties) After the UTS have been approved by the module leader, the unit testing of the form is accomplished in three steps: MODULE TESTING

31

The testing of individual modules as completed during the design phase itself. Each module was tested at the tested at the time of coding as well as whenever there were any modifications required. The emphasis was not only on the functionality of the software but also on the quality of the written code. Software coding standards for good quality of software were adhered to. INTEGRATION TESTING Once the different modules were thoroughly tested, they were combined i.e. integrated to make the system work as a whole and its performance was evaluated. Tests were performed for proper functionality of the system and results were evaluated for different data conditions. Integration testing is the testing of the interfaces among system modules. In other words, it ensures that the data moving between the modules is handled as intended. SYSTEM TESTING In next level the System is tested with all the components of application. System testing is the testing of the system against its initial objectives. It is done either in a simulated environment or in a live environment. The Project Leader or System Analyst tests all the components to see that they interact correctly when combined as a one product. A series of testing are performed for newly developed systems before the system is ready for the users acceptance testing. USER ACCEPTANCE TESTING After the system is completely ready for the installation the most important test has to be performed i.e. user acceptance testing because the system has to satisfy the users requirement and only when the user is fully satisfied and approves the system, the system can be installed.

32

The System is tested for the user acceptance by constantly keeping in touch with prospective system users at the time of development and changes were made wherever required. Input and output design. Menu used in application is descriptive enough to work with. Output reports are sufficient for the requirements. There are three levels of testing: Verification Testing runs the system in a simulated environment using simulated data. This simulated test is sometimes called alpha testing the simulated test is primarily looking for errors and omission regarding end user and design specification that were specified in the earlier phases but not fulfilled during construction. Validation Testing runs the system in a live environment using the real data. This sometimes called beta testing. Validation succeeds when the software functions in a manner that can be reasonably expected by the customer. Software validation has been achieved through series of black box testing that demonstrate with the requirements. Deviations and errors have been corrected at this step. During this validation, we are testing a number of items, including Systems Performance Peak workload processing performance Human engineering test. Methods and procedures test. Backup and Recovery testing.

33

Audit Testing certifies that the system is free of errors and is ready to be placed into operation not all organization requiring an audit. But many firms have an independent audit or quality assurance staff that must certify a systems acceptability and documentation before that system is placed into final operation. There are independent companies that perform systems and software certification for end users organizations.

STRESS TESTING

Applying Stress to a program means that a large amount of data is fed for processing in short period of time. In other words, consumption of computer resources is drastically raised in that time frame with the intention to ensure that the system will still perform effectively if the same condition occurs in the future. For each data entry screen, I prepared test data with the extreme values and tested under all relevant test conditions. After my own satisfaction, I invited the concerned user to test the relevant data entry screen against real data. This process helps in rectifying/modifying the modules, again and again. OUTPUT TESTING

The output generated by the system under consideration is in the format required by the users. And the information in the reports is accurate and reliable. The output reports are in the appropriate formats with meaningful headings and the footers.

34

35

BENEFITS PROJECT

OF

PROPOSED

By computerizing the system, all of the current problems can be solved. Beside this, there are some more benefits which are written below:1) Lots of time will be saved. 2) Easy alternation of data. 3) Back-up facility for the files. 4) Billing becomes easy. 5) Errors can be handed and removed very easily. 6) The system is such that it stands up to users

satisfaction.

36

ENTITY-RELATIONSHIP DIAGRAM
It is tool for problem analysis often called as E-R diagram. It was originally proposed by Petersen for the design of relational database systems and has been extended by others. Its detailed logical representation of the data from an organization and uses three main constructs i.e. data entities, relationships, and their associated attributes.

ENTITIES
An entities is a fundamental thing of an organization about which data may be maintained. An entity type is the description of all entities to which a common definition and common relationships and attributes apply. Entity type is represented with the help of rectangular, name of entity is written inside it.

RELATIONSHIPS
A relationship is a reason for associating two entity types. These relationships are sometimes called binary relationship because they involve two entity types. Some forms of data model allow more than two entity types to

37

be associated. Relationships are represented by diamond notation in E-R diagram.

VISUAL BASIC
Visual basic, is the fastest and easiest way to create applications for Microsoft Windows. Whether we are an experienced professional or brand new to windows programming. Visual basic provides you with a set of tools to simplify rapid application development. In visual Basic, visual part refers to the method used to create the graphical user interface (GUI). Rather than writing numerous lines of code to describe the appearance and location of interface elements, we simply add prebuilt objects into place on screen. If youve ever used a drawing program such as paint, we already have most of the skills necessary to create an effective user interface. The Basic part refers to he basic (Beginners All Purpose symbolic Instruction Code) language, a language used by more programmers than any other language in the history of computing. Visual Basic has evolved from the original BASIC language and now contains several hundred statements, functions and keywords many of which relate directly to the Windows GUI. Beginners can create useful applications by learning just a few of the keywords, yet
38

the

power

of

the

language

allows

professionals

to

accomplish anything that can be accomplished using ant other Windows programming language. The Visual Basic programming language is not unique to Visual Basic. The Visual Basic programming system, Applications Edition included in Microsoft Excel, Microsoft Access and many other Windows applications uses the same language. The Visual Basic Scripting Edition (VBSCRIPT) is a widely used scripting language and a subject of the Visual Basic language. The investment you make in learning Visual Basic will carry over to these other areas. Data access features allow us to create databases, frontend applications and scalable server-side components for most popular database formats including Microsoft SQL Server and other enterprise-level databases. ActiveX
TM

technologies allow us to use the functionality Microsoft Excel Spreadsheet and other

provided by other applications such as Microsoft Word Processor, Windows applications. We can even automate applications and objects created using the Professional or Enterprise editions of Visual Basic. Internet capabilities make it easy to provide access to documents and applications across the internet or intranet

39

from within our application, or to create Internet Server applications. Our finished application is a true.exe file that uses a Virtual Basic Virtual Machine that we can freely distribute.

Visual Basic Concept

In order to understand the application development process, it is helpful to understand some of the key concepts upon which Visual Basic is built. Because Visual Basic is a Windows development language, some familiarity with the Windows environment is necessary. If we are new to Windows programming, we need to aware of some fundamental differences between programming for Windows versus other environment.

How Windows Works: Windows, Events and Messages

A complete discussion of the inner workings of Windows would require an entire book. A deep understanding of all of the technical details isnt necessary. A simplified version of the working of windows involves three key concepts: windows, events and messages.

40

Think of a window as simply a rectangular region with its own boundaries. We are probably already aware of several different types of windows: an Explorer window in Windows95, a document Window within our word processing program, or a dialog box that pops up to remind us of an appointment. While these are the most common examples, there are actually many other types

of windows. A command button is a window. Icons, text boxes, option button and menu bars are all windows. The Microsoft windows operating system manages all of these many windows by assigning each one a unique id number. The system continually monitors each of these windows for signs of activity or events. Events can occur through user actions such as a mouse click or a key press, through programmatic control, or even as a result of another windows actions. Each time an event occurs, it causes a message to be sent to the operating system. The system processes the message and broadcasts it to the other windows. Each window can take the appropriate action based on its own instruction for dealing with that message (for example, repainting itself when it has been uncovered by another window).

41

Understanding Model

the

Event-Driven

In traditional or procedural applications, the application itself controls which portions of code execute and in what sequence. Execution starts with the first line of code and follows a predefined path through the application, calling procedures as needed. In an event-driven application, the code doesnt follow a predetermined path ---it executes different code sections in response to events. Events can be triggered by the users action, by message from the system or other itself. applications, The or even of from the applications determines sequence these events

the sequence in which the code executes, thus the path through the applications code differs each time the program runs. Because we cant predict the sequence of events, our code must make certain assumptions about the state of the world when it executes. When we make assumptions, we should structure our application in such a way as to make sure that the assumptions will always be valid.

42

Our code can also trigger events during execution. For example, programmatically changing the text in a text box cause the text boxs change event to occur. This will cause the code (if any) contained in the change event to execute. If we assumed that this event would only be triggered by user interaction, we might see unexpected results. It is for this reason that it is important to understand the event-driven model and keep it in mind when designing our application.

Interactive development
The traditional application development process can be broken into three distinct steps: writing, compiling and testing code. Unlike traditional languages, visual basic uses an interactive approach to development, blurring the distinction between the three steps. With most languages, if we make a mistake in writing our code, the error is caught by the compiler when we start to compile our application. We must then find and fix the error and begin the compile cycle again, repeating the process for each error found. Visual Basic interprets our code as we enter it, catching and highlighting most syntax or spelling errors on the fly. Its is almost like having an expert watching over our shoulder as we enter our code.
43

In addition to catching errors on the fly, Visual Basic also partially compiles the code as it is entered. When we are ready to run and test our applications, there is only a brief delay to finish compiling. If the compiler finds an array, it is highlighted in our code. We can fix the error and continue compiling without having to start over. Because of the interactive nature of Visual Basic, we will find ourselves running our application frequently as we develop it. This way we can test the effects of our code as we work rather than waiting to compile later.

SDI or MDI Interface

Two different styles are available for the Visual Basic IDE: single document interface (SDI) or multiple document interface (MDI). With the SDI option, all of the IDE windows are free to move anywhere on the screen; as long as Visual Basic is the current application, they will remain on top of any other applications. With the MDI option, all of the IDE windows are contained within a single resizable parent window.

ADO
The two corner stones of Universal Data Access are ActiveX Data Objects (ADO) and OLE for Databases (OLE DB). OLE DB is a layer
44

that sits on top of the database. ADO sits on top of OLE DB and offers a simplified view of the database. Because each database exposes its functionality with its own sets of API (applications programming interface) functions, to access each database through its native interface, we would have to learn the species of the database (lowlevel, technical details).

Features
ADO supports key features for building client/server and web based applications, including the following:

Independently created objects

Unlike Data Access Objects (DAO) or Remote Data Objects (RDO), we no longer have to navigate through a hierarchy to create objects because most ADO objects can be independently created. This allows us to create and track only the objects we need, and also results in fewer ADO objects and thus a smaller working set. Batch updating helps improve performance by locally caching changes to data, thus writing them all to the server in a single update.

Supports for stored procedures with in/out parameters and return values.Different cursor types, including the potential for support of back-end specific cursors.
45

Support for limits on number of returned rows and other query goals for performance. Support for multiple record sets returned from stored procedures or batch statements.

Database
Database is a collection of data. Our phone book is a simple database and so our checkbook. A history of a companys orders, invoices and payments is an example of a more complicated database, as is a log of salespersons contracts with clients and any related follow-up plans.

Ms-Access
In Ms-Access a database is a collection of information that is related to a particular subject stored in the form of table. Ms-Access is a very powerful RDBMS which manages data in term of special table called relation. Using Ms-Access we can manage all information from a single database file. Database files are stored with extension .mdb.

What can Access do for us?

Access stores information in the form of tables and build our database on its bases. Each row in a table holds all informations and for a particular person it is called a record and each column contains different pieces of information.
46

In Access we have few things known as Tables, Form, Reports and Queries. They allow us to check and get desired information as and when required.

TABLES: - Tables of database looks like a college

time-table or spreadsheet. Each table holds data like relating to a

particular subject. The information is arranged in

rows and columns. Each row in a table is record.

QUERY: - Query is the way to ask questions and

get answer from the database. For example, we would like to ask, how many students have got 80% and above percentage etc.

REPORT: - Summarized information from one or

more table can be presented in a very attractive format. It become easy to read and understand information.

TECHNOLOGIES
ActiveX Data Objects ActiveX: An ActiveX control is an extension to the visual basic toolbox. We use ActiveX just as we would any of the standard built-in controls, such as the checkbox control. When we add an ActiveX control to a program, it becomes part of the development and runtime environment and provides new functionality for our application.

47

ActiveX controls leverage our capabilities as a Visual Basic Programmer by retaining some familiar properties, property, however, properties events and methods such as the name Then and and which behave the ActiveX that greatly as we would expect. increase our flexibility

controls feature methods

capability as a visual basic programmer. In Visual basic, three data access interfaces are available to us: ActiveX data Object (ADO), remote Data Object (RDO) and Data Access Object (DAO). A Data Access Interface is an object model that represents various facts of accessing data. Using Visual Basic, we can programmatically control the connection, statements builders and returned data for use in any application. For new projects we should use Ado as our data access interface.

Why use ADO?

Ado is designed as an easy-to use application level interface to Microsofts newest and most powerful data access paradigm, OLEDB. OLEDB provide high performance access to any data source, including rational and non rational databases, email and file systems, text and graphics, custom business objects and more. ADO is implemented for minimal network traffic key.

48

Internet scenarios and a minimal number of layers between the front-end and data source-all to provide a lightweight, high performance interface. ADO is called using a familiar metaphor-the OLE automation interface. And ADO uses conventions and features similar to DAO and RDO, with simplified semantics that make it easy to learn. OLE The OLE (Object Linking and Embedding) is a method for sharing data between windows based applications. OLE allows us to develop an application where we can access the best features from many different Windows based applications.

49

OPERATING SYSTEM
Windows XP
The operating system for personal computers (PCs) in the early 1980 was DOS. DOS is a single user, characterbased operating system. Microsoft Corporation started working on developing a graphic user interface (GUI) for PCs in 1983. Microsoft came out with a few versions of Windows, such as Windows 1, Windows 2.0 and Windows 386 during 1985 to 1988. However, these versions did not become popular as the software was not very powerful and user-friendly and PCs in those days did not have CPU power and memory. Windows 3, announced in 1990 was the first Windows program that was accepted by the user and software develops on large scale. In 1992, Microsoft corporation announced Windows 3.1, the enhanced and update version of Windows 3. Windows 3.1 (or its variations, such as Windows 3 and 3.11) is not full fledged operating system. It is a program that runs over DOS. It enhances the power and use of a PC running DOS in the following ways: It converts the plain character-based user interfaced provided by DOS in to a Graphical User Interface (GUI). It makes the computers easy as users are not required to

50

remember and type commands. Instead, users can click the little picture (called Icons) that represent commands to run programs.

It provides multitasking capabilities to the PC. A PC running DOS can run only one program (task) at a time. For instance, if we are running a word processor on a DOS based PC, we can not simultaneously run the Spread-sheet program. However, Windows converts a PC that could run just one program into a PC that can run two or more tasks simultaneously. The number of tasks that our Windows-based PC can run depends on the amount of RAM available in our PC. Unlike DOS, that displays information in characters of the same size, Windows can use different fonts i.e. different shapes and sizes of characters can be displayed and printed. True Type fonts introduced in Windows 3.1 appear the same on the monitor as well on the printed page.

51

Windows XP introduced by Microsoft Corporation almost at the same time, is a complete operating system. Besides operating system, Windows NT also introduces the Networking Software. This means that is to connect several PCs running Window 95, we dont need a separate network operating system such as NetWare. In 1995, Microsoft introduces Windows 95. Windows 95 is a fullfledge operating system. Microsoft came out with an update and enhanced version of Windows 95 in the form of Windows 98. Again Windows 98 was a runway success. Microsoft already released Windows 2000, an update version of Windows 98 in the beginning of 2000. After Windows 2000, Microsoft introduces Windows XP series such as Windows XP-SP1, Windows XP-SP2 etc. These days most new PCs come with Windows XP-SP2 preinstalled. Besides providing the basic operating capabilities to our PC, Windows 95/98 comes with a number of useful programs. It has its own Windows Explorer that can help us to copy and move files and manage directories. Windows also come with a number of useful applications, such as mini word processor (word pad), disks. a drawing program (paint), calendar, clock, calculator and notepad and system tools to manage hard

52

CHOICE OF LANGUAGE AND TOOL FOR DEVELOPMENT In the software development some activities are performed after the main development is complete. Implementation phase is concerned with the actual installation of the software on the computer and then testing it. Two types of specification are required to implement the system; these are software and hardware requirements. System implementation is described in two sections: Firstly, the implementation of the Personal Information System as front ends in Visual Basic 6.0 and back end as SQL Server. VISUAL BASIC 6.0 DEVELOPMENT SYSTEM Visual Basic is an event driven programming language. Programming in Visual Basic is done visually, which means that as you design your application you will know how your application will look on execution. You can therefore change and experiment with the design to meet your requirement. The main advantage of Visual Basic is that it is Rapid application Development Tool. This is the main reason why Visual Basic is extensively as a prototyping type of language. The predecessor of Visual Basic was BASIC (Beginner All Purpose Symbolic Instruction Code). Basic was mainly interpreterbased language whereas Visual Basic is partly interpreter-based and partly compiler-based. Also Visual Basic supports the OOP but there was no concept of OOP in BASIC. Visual Basic works with all the RDBMS without any problems and provides easy methods for inserting, updating and accessing the data from the database.

53

Three editions of Visual Basic are available. o Standard o Enterprise o Professional STANDARD EDITION The Visual Basic standard Edition:
o

Allow you to create powerful 32-bit applications for Microsoft Windows 9 xs and Windows NT.

o Includes intrinsic controls, as well as Grid, and data-Bound controls.

o

Includes learn Visual Basic Now (a multimedia CD-ROM title), a printed programmers guide and On-line Help.

o Includes Microsoft Developer Network CDs containing full online documentation. PROFESSIONAL EDITION The professional edition, in addition to the features provided in the standard edition (except the multimedia title), includes o Active X controls, including Internet Controls. o Internet Information Server (IIS) Application Designer o Integrated Data Tools and Data Environment o DHTML Page Designer ENTERPRISE EDITION o The Enterprise edition, in addition to the features provided in the Professional edition, allows creation of robust distributed application and includes: o Application Performance Explorer o Internet Information Services o Support for Microsoft Transaction Server 2.0 o Stored Procedure Editor o SQL Debugging o Visual Component Manager o Visual Database Tool o Visual Source Safe (VSS)

54

FEATURES OF Visual Basic 6.0 Visual Basic 6.0 has many powerful features that required in todays programming environment, which include features from the previous versions also. Some of these features are discussed below: Based on Basic language. Programming objects and events: the visual forms and objects like list boxes and radio buttons that you use on the forms, help you to interest with the application in order to find out the flow of the program. The forms and objects perform and specified action when event occurs. That is why Visual Basic is known as the Event-Driven programming language.
o

o o

A common programming plate for across all Microsoft office applications: Almost all Microsoft applications support Visual Basic by sharing and reusing code across application. Native Code Compilation: One of the most significant features of Visual Basic is Native Code Compilation. This compilation produces code almost 20 times faster than the pseudo code compilation 32-bit support: Visual Basic supports 32-bit applications A quick and easy way to develop applications: the tools provided by Visual Basic help you reduce the development time because it is faster to develop application using the tool available. Wizards: visual Basic includes many wizards that can

o o

automate tasks or events automate coding. Visual Basic 6.0 has a new collection of wizards to perform some difficult and routine tasks. Some of these are:

The package and deployment Wizard. The Class Builder Utility

55

 Data Object Generator Wizard The Add-In Designer The Application wizard

Object Type: New object types, called File System Object or FSO, have been added to Visual Basic 6.0. These objects enable you to work faster and more easily with files and directories. Functions: there are fourteen additional functions in Visual Basic 6.0. All of them deal with string data. Some of these are CallByName, Filter, Format Currency, Format Date Time, Format Number and Format Percent.

ActiveX features: Visual Basic allows imagining applications to an ActiveX document, which enables the application to install and run from a Web Browser. Thus, the developer need not know languages like Java or HTML. Visual Basic also enables you to create ActiveX controls. New ActiveX controls have been enhanced in Visual Basic 6.0. Database Enhancement: Earlier version of Visual Basic used Data Access Objects (DAO) and Remote Data Objects (RDO). Visual Basic 6.0 includes ActiveX Data Object (ADO) as the visual data access tool. Data access features allows you to create databases and front-end application for most popular database formats, including Microsoft SQL Server and other enterprise-level databases. ADO requires very little coding to interact with a data source. SDI/MDI/Explorer style Interface Options: Visual Basic has the functionality to create single, multiple, or windows explorer style document interface applications. N-tier architecture: The traditional client/server architecture included two parts, also called the tiers, the client and the server. Today we have n-tier client/server architecture, which include more than two tires. The applications using n-tier architecture can be divided into a minimum of three parts, namely interface, business logic, and database functions. The

56

client and the server handle the processing and the middle layer takes care of the business logic.
o

User Interface and Navigation: It provides a graphical interface for you to interact with the applications, view results of requests, manipulate and format the data once the client receives it. Business Logic: This is the second tier, which captures the rules that govern the application processing, and connects the user with the data. Data Services: This tier manages and provides access to application data from a structured or an unstructured store.

Package and Deployment Wizard:

The package and

Deployment Wizard, previously called Setup Wizard, has been enhanced to include a wider range of data access formats like ADO, DAO, ODBC, and RDO. A Visual Basic project is compressed into a CAB file with an executable setup program. The package can be deployed on a distribution site, like the Internet Serer, or just moved to a local or network folder. VISUAL BASIC DEVELOPMENT ENVIRONMENT The Visual Basic Development environment allows us to develop applications using Visual Basic 6.0. it provides facilities for designing an application using Visual Basic Standard Controls, running and testing the applications. It consists of the following items: MENU BAR The menu bar helps you to perform various tasks and it includes a list of options. Each option on the menu bar has a drop-down list of items that are related to the option chosen from the menu bar. FORM A from is one of the main building blocks of Visual Basic application. Users interact with the controls on a form to obtain the desired result. Most of the applications written in Visual Basic include at least one form.

57

PROJECT EXPLORER A project window gives a list of forms and modules in the current project. A project is a collection of files used to build the applications. TOOL BOX The toolbox is a window that provides you a set of tools that are used at design time to place controls on a form. PROPERTIES WINDOWS The properties window lists the property settings for the forms or controls that you select. A property is a characteristic of an object, such as size, caption or color. The property window displays the property of only one object at a time the one that is currently selected. CODE EDITOR The Visual basic code editor is the window where most of the code is written. It is a special word processor with a number of features that help you to write a Visual Basic Code easily. OBJECT BROWESER The Object Browser is another window available from the view menu. It gives a list of objects that can be used in the project and gives you a quick way to navigate through the code. It also displays classes, properties, methods events and constants in your project. Objects from other applications can also be used. FORM LAYOUT WINDOW Form layout window allows you to visually poison the forms at design time. All forms that are visible in the environment are shown in the form layout window. CONTEXT MENU Visual Basic provides context menus that contain short cuts to the frequently performed actions. To open a context menu, you need to click the right mouse button on the project being used. STANDARD TOOLBAR The standard toolbar has buttons for the most frequently used commands in Visual Basic. Some of them are Open Project, Save

58

Project, Cut, Copy, Paste, Start, Break and Add Form. It can also contain buttons for the TOOL Box, the properties Window and other features. EVENT ORIENTED LANGUAGE Visual Basic is an event driven language. In older pre-GUI systems such as DOS, commands are sent to programs through command line or through a series of sequential menus. In this approach only one thing could happen at a time. These user interfaces were extremely sequential; one thing followed the other in a predictable manner. In these DOS based programs once an application was run it takes the control and the user has no control over the flow of the program execution. In Windows based programming, window keeps the control, when any event occurs, such as key press or mouse down; it sends a message to the appropriate program and temporarily gives the control to that program to take the proper action response to the event. These events were handled through an event loop. The event loop receives each event and routed to the proper routine. But the problem was this event loop has to be written by hand. Visual Basic provides the complete event loop, built into the development system as well as default routines to handle most common routine. OUTSIDE RESOURCES One of the great advantages of being a Visual Basic Programmer is the ability to use many resources outside the Visual Basic Development Environment to accomplish programming tasks. These include ability to use commercial or customized component plug-in, the setup wizard, the windows API (build into Windows), the help compiler, and ODBC drivers (many include with Visual Basic). These tools provide a wealth of possibilities to shrink the

59

time it takes to develop a project increase the number of features and provide the ease of use required in a modern program. PLUG-IN COMPONENTS (DLL, VBX, OCX) Plug-in components are precompiled pieces of code that usually do one particular task very well. HELP COMPILER Help files are great bonus included in the Windows Systems. Visual Basic includes a help compiler so one can create a complete help file to include with the application. Pressing the F1 key in the program will display the context sensitive help. One can searches the key words by clicking on a highlighted word and can get more information.
o

User Interface:

This is what the user interacts with. It

contains the forms that display the data and enable the user to view or update it. It also includes various data access techniques for database services like adding or deleting records and performing queries.
o

Database Engine: it is contained in a set of Dynamic Link Library (DLL) files and is linked with the Visual Basic program at run time. The engine is responsible for reading, writing and modifying the database. It also handles indexing, security and referential integrity issues in the database. It contains a query processor to handle SQL queries. The database engine is logically places between the program and the database files. Data Store: tables. For it is the set of files containing the database example Microsoft Access has .mdb files A data is said to be passive

containing several tables. DATA ACCESS METHODS

because it does not work on the data on its own. In Visual Basic, an application can access the data using a variety of methods. These are as follows:

60

o Data Access Objects (DAO) o Remote Data Objects (RDO) o ActiveX Data Objects (ADO) Out of these data access methods. The PIS, uses ADO method, as it is one of the best methods for accessing the database residing on a server. ActiveX Data Objects (ADO) Method ActiveX Data Objects (ADO) is Microsoft's strategic, highlevel interface to all kinds of data. ADO provides consistent, highperformance access to data, whether you're creating a front-end database client or middle-tier business object using an application, tool, language, or even an Internet browser. ADO is an object interface to OLE. ADO is the single data interface you need to know for 1- to n-tier client/server and Web-based data-driven solution development. ADO provides an Object oriented programming interface for accessing a data source by using an OLEDB data provider. ADOs provide fast and easy access to all types of data. The ADO model has three main components. Connection Object Command Object Recordset Object The ADO Model differs from the DAO and RDO models in that many of the objects can be created independently or one another e.g. you can create a recordset object without first creating a connection object. ADO implicitly creates the required connection objects for you.

61

SCOPE OF WORK
The system has and been designed of according the to the specifications requirements Horticulture

Department. It has been developed in such a way that each module is self contained and any single module can be modified or new modules may be added without affecting the existing modules. The system can be easily enhanced in future, if required. Every software has room for expansion. Likewise this software too would be modified and new improved features will be incorporated into it. The System would be modified to include Additional Reports for the proper analysis and monitoring of the operations.

62

63

Login.frm Private Sub Command1_Click(Index As Integer) welcome.Show End Sub Private Sub Command2_Click() End End Sub

64

Welome.frm Private Sub Command1_Click() customer1.Show End Sub Private Sub Command2_Click() supplier1.Show End Sub Private Sub Command3_Click() End End Sub

65

Customer1.frm Private Sub Command1_Click() customer.Show End Sub Private Sub Command2_Click() vehpurchase.Show End Sub Private Sub Command3_Click() payment.Show End Sub Private Sub Command4_Click() finance.Show End Sub Private Sub Command5_Click() reciept.Show End Sub Private Sub Command6_Click() welcome.Show End Sub

66

Customer.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer
67

If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

68

Vehpurchase.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show End Sub
69

Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

70

Payment.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show
71

End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

72

Finance.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show
73

End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

74

Receipt.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show
75

End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

76

Supplier1.frm Private Sub Command1_Click() service.Show End Sub Private Sub Command2_Click() salesman.Show End Sub Private Sub Command3_Click() insurance.Show End Sub Private Sub Command4_Click() welcome.Show End Sub

77

Service.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click()
78

supplier1.Show End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click()
79

Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() customer1.Show End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

80

Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub Salesman.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search"))
81

b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click() supplier1.Show End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

82

Insurance.frm Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Data1.Recordset.Delete Data1.Recordset.MoveNext If Data1.Recordset.EOF Then Data1.Recordset.MoveLast End If End Sub Private Sub Command3_Click() Data1.Recordset.Update End Sub Private Sub Command4_Click() Dim X As String X = (InputBox("enter customer", "search")) b = "customer_id=" & X Data1.Recordset.FindFirst b End Sub Private Sub Command5_Click() End End Sub Private Sub Command6_Click()
83

supplier1.Show End Sub Private Sub data1_validate(Action As Integer, save As Integer) Dim iresponse As Integer If save = True Then iresponse = MsgBox("save changes", vbYesNo) If iresponse = vbNo Then save = False Data1.UpdateControls 'refreshfields End If End If End Sub

84

85

86

87

88

89

90

91

92

93

94

BIBLOGRAPHY

S.NO 1 2 3 4 5

Name of the Book System Analysis and Design MS-Access Introduction to database Management System Mastering Visual Basic 6.0

Author Awadh R.B Patel Bipin C Evangelos Petroutsos Petroutsos

Mastering Database programming

95