CHAPTER-1

INTRODUCTION

1.1 Overview:-

It is the complete medical shop management software is so designed as to ease the work load of medical shop professionals. The main feature includes invoicing, inventory and stock control, accounting, client and vendor management.

This software helps you to track all the profits, loss, profitable clients and products of medical shop moreover it’s a medical shop accounting software. Flexible and adaptive software suited to medical shops or stores or pharmacies of any size.

Current System Features:-

Ø Menu driven, Key board and mouse navigation

Ø Paperless practice

Ø Improve efficiency, productivity

Ø Cost effective solutions

Ø Graphical User Interface with Context Sensitive Help

Ø Automatic importing of drug list

Ø Inbuilt account group and account ledgers

Ø Option for setting default company

Ø Keep address book / telephone directory for easy access

Ø Option for setting default company

Limitations of current system:-

Ø We can’t view a financial report of past financial year

Ø We can’t created multiple companies with different financial year

Ø Not maintain all financial report and financial statements such as day book, profit and loss amount and balance sheet

Ø It allows only one user therefore it is not provide a high security

Ø Not have a better search option for finding available product of company

Ø It provide only 50 reports

Ø Special training needed for using the system

Ø Accounting knowledge is must for use this system

Proposed system:-

This System will store the information of medicines & customers in the system. It will also store the information about stock details. This system provides security by granting access rights for changing the sensitive data to administrator only. Customized search options are also available in this system. This system can generate all kinds of reports as per the user’s requirements.

Proposed system feature:-

Ø Multiple companies with different financial year can be created

Ø We can view report of past financial year

Ø Back up and restore facility

Ø Keep record of daily customers

Ø Keep records of salesmen

Ø Tracking sales done by a particular salesman

Ø Manage counter sale

Ø Keep track of instant collecting medicines from near by medical shop and selling directly

Ø Reminders for product low stock, product short expiry

Ø Keeps track of all payment , receipt of company

Ø Creating different users with different privilege level for providing high security

Ø Handle financial accounting.

Ø Provides around 100 reports with maximum filtering option

Ø Better search option for finding available products of company

Ø Search can be filtered by product group, product, shelf,

Manufacture etc

Ø Record various events of day which can be viewed as event calendar

Chapter -2

DEVELOPMENT ENVIRONMENT

2.1 HARDWAR SPECIFICATION:-

Processor : Pentium IV

RAM : 512 MB

Hard disk : 40 GB

2.2 SOFTWARE SPECIFICATION:-

Platform : Windows 98

Front end : VB.NET 2008

Back end : SQL Server 2005

2.3 ABOUT VB.Net

Overview of the .NET Framework:-

The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
To provide a code-execution environment that minimizes software deployment and versioning conflicts.
To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic.

Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code (similar to Microsoft® ActiveX® controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and secure isolated file storage.

The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture.

Features of the Common Language Runtime:-

The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime.

With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application.

The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally featuring rich.

The runtime also enforces code robustness by implementing a strict type- and code-verification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety.

In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications.

While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance.

Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework.

For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services:

· Console applications.

· Scripted or hosted applications.

· Windows GUI applications (Windows Forms).

· ASP.NET applications.

· XML Web services.

· Windows services.

For example, the Windows Forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes.

Client Application Development:-

Client applications are the closest to a traditional style of application in Windows-based programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers.

Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.

In the past, developers created such applications using C/C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products into a single, consistent development environment that drastically simplifies the development of client applications.

The Windows Forms classes contained in the .NET Framework are designed to be used for GUI development. You can easily create command windows, buttons, menus, toolbars, and other screen elements with the flexibility necessary to accommodate shifting business needs.

For example, the .NET Framework provides simple properties to adjust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is one of many ways in which the .NET Framework integrates the developer interface, making coding simpler and more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer. This means that binary or natively executing code can access some of the resources on the user's system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user's system can now be safely deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page.

Server Application Development:-

Server-side applications in the managed world are implemented through runtime hosts. Unmanaged applications host the common language runtime, which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server.

The following illustration shows a basic network schema with managed code running in different server environments. Servers such as IIS and SQL Server can perform standard operations while your application logic executes through the managed code.

Introduction to Windows Forms (Visual Basic.NET):-

Windows Forms is the new platform for Microsoft Windows application development, based on the .NET Framework. This framework provides a clear, object-oriented, extensible set of classes that enable you to develop rich Windows applications. Additionally, Windows Forms can act as the local user interface in a multi-tier distributed solution. Windows Forms is a framework for building Windows client applications that utilize the common language runtime. Windows Forms applications can be written in any language that the common language runtime supports.

What Is a Form?

A form is a bit of screen real estate, usually rectangular, that you can use to present information to the user and to accept input from the user. Forms can be standard windows, multiple document interface (MDI) windows, dialog boxes, or display surfaces for graphical routines. The easiest way to define the user interface for a form is to place controls on its surface. Forms are objects that expose properties which define their appearance, methods which define their behavior, and events which define their interaction with the user. By setting the properties of the form and writing code to respond to its events, you customize the object to meet the requirements of your application.

As with all objects in the .NET Framework, forms are instances of classes. The form you create with the Windows Forms Designer is a class, and when you display an instance of the form at run time, this class is the template used to create the form. The framework also allows you to inherit from existing forms to add functionality or modify existing behavior. When you add a form to your project, you can choose whether it inherits from the Form class provided by the framework, or from a form you have previously created.

Additionally, forms are controls, because they inherit from the Control class.

Within a Windows Forms project, the form is the primary vehicle for user interaction. By combining different sets of controls and writing code, you can elicit information from the user and respond to it, work with existing stores of data, and query and write back to the file system and registry on the user's local computer.

Although the form can be created entirely in the Code Editor, it is easier to use the Windows Forms Designer to create and modify forms.

Some of the advantages of using Windows Forms include the following:

Simplicity and power: Windows Forms is a programming model for developing Windows applications that combines the simplicity of the Visual Basic 6.0 programming model with the power and flexibility of the common language runtime.

Lower total cost of ownership: Windows Forms takes advantage of the versioning and deployment features of the common language runtime to offer reduced deployment costs and higher application robustness over time. This significantly lowers the maintenance costs (TCO) for applications written in Windows Forms.

Architecture for controls: Windows Forms offers an architecture for controls and control containers that is based on concrete implementation of the control and container classes. This significantly reduces control-container interoperability issues.

Security: Windows Forms takes full advantage of the security features of the common language runtime. This means that Windows Forms can be used implement everything from an untrusted control running in the browser to a fully trusted application installed on a user's hard disk.
XML Web services support: Windows Forms offers full support for quickly and easily connecting to XML Web services.

Rich graphics: Windows Forms is one of the first ship vehicles for GDI+, a new version of the Windows Graphical Device Interface (GDI) that supports alpha blending, texture brushes, advanced transforms, rich text support, and more.

Flexible controls: Windows Forms offers a rich set of controls that encompass all of the controls offered by Windows. These controls also offer new features, such as "flat look" styles for buttons, radio buttons, and check boxes.

Data awareness: Windows Forms offers full support for the ADO data model.

ActiveX control support: Windows Forms offers full support for ActiveX controls. You can easily host ActiveX controls in a Windows Forms application. You can also host a Windows Forms control as an ActiveX control.

Licensing: Windows Forms takes advantage of the common language runtime enhanced licensing model.

Accessibility: Windows Forms controls implement the interfaces defined by Microsoft Active Accessibility (MSAA), which make it simple to build applications that support accessibility aids, such as screen readers.

Design-time support: Windows Forms takes full advantage of the meta-data and component model features offered by the common language runtime to provide thorough design-time support for both control users and control implementers.

Crystal Reports :-

Crystal Reports for Visual Basic .NET is the standard reporting tool for Visual Basic.NET; it brings the ability to create interactive, presentation-quality content — which has been the strength of Crystal Reports for years — to the .NET platform.

With Crystal Reports for Visual Basic.NET, you can host reports on Web and Windows platforms and publish Crystal reports as Report Web Services on a Web server.

To present data to users, you could write code to loop through recordsets and print them inside your Windows or Web application. However, any work beyond basic formatting can be complicated: consolidations, multiple level totals, charting, and conditional formatting are difficult to program.

With Crystal Reports for Visual Studio .NET, you can quickly create complex and professional-looking reports. Instead of coding, you use the Crystal Report Designer interface to create and format the report you need. The powerful Report Engine processes the formatting, grouping, and charting criteria you specify.

Report Experts

Using the Crystal Report Experts, you can quickly create reports based on your development needs:

· Choose from report layout options ranging from standard reports to form letters, or build your own report from scratch.

· Display charts that users can drill down on to view detailed report data.

· Calculate summaries, subtotals, and percentages on grouped data.

· Show TopN or BottomN results of data.

· Conditionally format text and rotate text objects.

ACTIVE X DATA OBJECTS

In Visual Basic .Net, three data access interfaces are available: Active X Data Objects( ADO), Remote Data Objects (RDO) and Data Access Objects (DAO). These access interfaces are used to access the data from database.

Why use ADO?

Consistently accessing data within the enterprise is a challenge for today's business applications. ODBC provides the first step toward overcoming this challenge by enabling applications to access relational databases. However, as developers and system architects want to include nonrelational data sources and to work in environments such as the Internet, they encounter the dilemma of either developing their own data-access paradigms or working with application program interfaces (APIs) that are incompatible in the new environments. Microsoft® ActiveX® Data Objects (ADO) along with OLEDB solves this dilemma by providing a single model that works with all data sources in a variety of environments.

ADO provides consistent, high-performance 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 the single data interface you need for developing 1- to n-tier client/server and Web-based, data-driven solutions.

This paper introduces ADO and the ADO programming model for application developers who are targeting Microsoft SQL Server™. Particular attention is given to taking advantage of SQL Server features with ADO, such as stored procedures and server cursors. The concepts presented in the sections titled "The ADO Object Model" and "Using ADO with Visual Basic, VBScript, Visual C++, and Java" are applicable to all ADO programmers.

ADO Overview

ADO was first introduced as the data access interface in Microsoft Internet Information Server (IIS). ADO is easy to use because it is called using a familiar metaphor: the Automation interface, available from just about any tool and language on the market today. Because of its popularity as an easy-to-use, lightweight interface to all kinds of data, and the growing need for an interface spanning many tools and languages, ADO is being enhanced to combine the best features of, and eventually replace, RDO and DAO, the data access interfaces in widest use today. ADO is in many ways similar to RDO and DAO. For example, it uses similar language conventions. ADO provides simpler semantics, which makes it easy to learn for today's developers.

ADO is designed to be the application-level interface to OLEDB, Microsoft's newest and most powerful data access paradigm. OLEDB provides high-performance access to any data source. Together ADO and OLEDB form the foundation of the Universal Data Access strategy. OLEDB enables universal access to any data. ADO makes it easy for developers to program. Because ADO is built on top of OLEDB, it benefits from the rich universal data access infrastructure that OLEDB provides.

OLEDB Providers

There are two types of OLEDB applications: consumers and providers. A consumer can be any application that uses or consumes OLEDB interfaces. For example, a Microsoft Visual C++® application that uses OLEDB interfaces to connect to a database server is an OLEDB consumer. The ADO object model that uses OLEDB interfaces is an OLEDB consumer. Any application that uses the ADO object model uses OLEDB interfaces indirectly through the ADO objects. An OLEDB provider implements OLEDB interfaces; therefore, an OLEDB provider allows consumers to access data in a uniform way through a known set of documented interfaces. In a sense, an OLEDB provider is similar to an ODBC driver that provides a uniform mechanism for accessing relational data. OLEDB providers not only provide a mechanism for relational data but also for nonrelational types of data. Furthermore, OLEDB providers are built on top of Component Object Model (COM) interfaces that allow more flexibility; whereas ODBC drivers build on top of a C API specification.

Microsoft OLEDB SDK version 1.1 shipped two OLEDB providers: the ODBC Provider and sample text provider. The sample text provider is an example that demonstrates the implementation detail of an OLEDB provider. The ODBC Provider is an OLEDB provider for ODBC drivers. This provider enables consumers to use the existing ODBC drivers without having to implement new OLEDB providers to replace existing ODBC drivers. With OLEDB version 2.0, providers for SQL Server, Oracle data, and Microsoft Jet databases were added to the SDK. For more information about OLEDB and OLEDB providers, see the OLEDB section of the Microsoft Data Access

The ODBC Provider

The ODBC Provider maps OLEDB interfaces to ODBC APIs. With the ODBC Provider, OLEDB consumers can connect to a database server through the existing ODBC drivers in the following process: A consumer calls an OLEDB interface on the ODBC Provider. The ODBC Provider invokes corresponding ODBC APIs and sends the requests to an ODBC driver.

Because the ODBC Provider allows OLEDB consumers to use existing ODBC drivers, there may be some performance concern about the additional layer of the ODBC Provider on top of the existing ODBC driver manager. The design goal of the ODBC Provider is to implement all the functionality of the ODBC driver manager; therefore, the ODBC driver manager is not needed. However, the ODBC Provider still requires the ODBC Driver Manager to support connection pooling with ODBC applications.

The ADO Object Model

The ADO object model defines a collection of programmable objects that you can use in Visual Basic, Visual C++, Microsoft Visual Basic, Scripting Edition, Java, and any platform that supports both COM and Automation. The ADO object model is designed to expose the most commonly used features of OLEDB.

The ADO object model contains their objects:

· Connection

· Command

· Recordset

The Connection Object

The Connection object allows you to establish a communication link with a data source. The Connection object provides a mechanism for initializing and establishing the connection, executing queries, and using transactions.

The underlying OLEDB provider used for connecting is not limited to the ODBC Provider; you can also use other providers for connecting. Specify a provider through the Provider property. If none is specified, MSDASQL (the ODBC provider) is the default provider used for the connection.

The Command Object

The Command object allows you to issue commands to the database. These commands can be, but are not limited to, query strings, prepared underlying provider for the database. The information and examples contained here focus on the Microsoft ODBC Provider that supports a wide variety of relational databases.

ABOUT ORACLE

DATABASE

A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, and Oracle. These systems allow users to create, update and extract information from their database.

A database is a structured collection of data. Data refers to the characteristics of people, things and events. Oracle stores each data item in its own fields. In oracle, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name.

During an Oracle Database design project, the analysis of your business needs identifies all the fields or attributes of interest. If your business needs change over time, you define any additional fields or change the definition of existing fields.

Oracle Tables

Oracle stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.

Primary Key

Every table in oracle has a field or a combination of fields that uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.

Relational Database

Sometimes all the information of interest to a business operation can be stored in one table. Oracle makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes oracle a relational database management system, or RDBMS. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables.

Foreign Key

When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key is a field or a group of fields in one table whose values match those of the primary key of another table.

Referential Integrity

Not only does Oracle allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.

Data Abstraction

A major prupose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels.

Physical level:

This is the lowest level of abstraction at which one describes how the data are actually stored.

Conceptual Level:

At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them.

View level:

This is the highest level of abstraction at which one describes only part of the database.

Advantages of RDBMS

· Redundancy can be avoided

· Inconsistency can be eliminated

· Data can be Shared

· Standards can be enforced

· Security restrictions ca be applied

· Integrity can be maintained

· Conflicting requirements can be balanced

· Data independence can be achieved.

Disadvantages of DBMS

A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgraded to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication, the lack of duplication requires that the database be adequately backed up so that in case of failure the data can be recovered.

FEATURES OF ORACLE (RDBMS)

ORACLE is the leading database management system (DBMS) because it is the only Database that meets the uncompromising requirements of today’s most demanding information systems. From complex decision support systems (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, Oracle leads the industry in both performance and capability

ORACLE is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous operation and support for every database.

ORACLE RDBMS is high performance fault tolerant DBMS which is specially designed for online transactions processing and for handling large database application.

ORACLE with transactions processing option offers two features which contribute to very high level of transaction processing throughput, which are

· The row level lock manager

· PL/SQL a procedural language extension to SQL

Enterprise wide Data Sharing:-

The unrivaled portability and connectivity of the ORACLE DBMS enables all the systems in the organization to be linked into a singular, integrated computing resource.

Portability:-

ORACLE is fully portable to more than 80 distinct hardware and operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This portability gives complete freedom to choose the database sever platform that meets the system requirements.

Open Systems:-

ORACLE offers a leading implementation of industry –standard SQL. Oracle’s open architecture integrates ORACLE and non –ORACLE DBMS with industries most comprehensive collection of tools, application, and third party software products Oracle’s Open architecture provides transparent access to data from other relational database and even non-relational database.

Distributed Data Sharing:-

Oracle’s networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was stored on a single local computer. A single SQL statement can access data at multiple sites. You can store data where system requirements such as performance, security or availability dictate.

Unmatched Performance

The most advanced architecture in the industry allows the ORACLE DBMS to deliver unmatched performance.

Sophisticated Concurrency Control

Real World applications demand access to critical data. With most database Systems application becomes “contention bound” – which performance is limited not by the CPU power or by disk I/O, but user waiting on one another for data access . Oracle employs full, unrestricted row-level locking and contention free queries to minimize and in many cases entirely eliminates contention wait times.

No I/O Bottlenecks

Oracle’s fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, oracle commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential writes typically group commit multiple transactions. Data read by the transaction remains as shared memory so that other transactions may access that data without reading it again from disk. Since fast commits write all data necessary to the recovery to the log file, modified blocks are written back to the database independently of the transaction commit, when written from memory to disk.

CHAPTER-3

SYSTEM ANALYSIS AND STUDY

3.1 Problem definition:

Limitations of current system:-

Ø We can’t view a financial report of past financial year

Ø We can’t created multiple companies with different financial year

Ø Not maintain all financial report and financial statements such as day book, profit and loss amount and balance sheet

Ø It allows only one user therefore it is not provide a high security

Ø Not have a better search option for finding available product of company

Ø It provide only 50 reports

Ø Special training needed for using the system

Ø Accounting knowledge is must for use this system

Proposed system:-

Proposed system feature:-

Ø Multiple companies with different financial year can be created

Ø We can view report of past financial year

Ø Back up and restore facility

Ø Keep record of daily customers

Ø Keep records of salesmen

Ø Tracking sales done by a particular salesman

Ø Manage counter sale

Ø Keep track of instant collecting medicines from near by medical shop and selling directly

Ø Reminders for product low stock, product short expiry

Ø Keeps track of all payment , receipt of company

Ø Creating different users with different privilege level for providing high security

Ø Handle financial accounting.

Ø Provides around 100 reports with maximum filtering option

Ø Better search option for finding available products of company

Ø Search can be filtered by product group, product, shelf,

Manufacture etc

Ø Record various events of day which can be viewed as event calendar

3.2 Feasibility study:

Feasibility is the determination of whether or not a project is worth going. The process followed in making this determination is called feasibility study. Once it has been determined that a project is feasible, then analyst can go a head and prepare the project specification which finalize project requirements.

TYPE OF FEASIBILITY

1) Technical Feasibility: This is concerned with specifying equipment and software that will successfully satisfies the user requirement. The technical feasibility includes the facility to produce outputs in a given time. The technical feasibility has the ability to process a certain volume of transaction at a particular speed.

2) Economical Feasibility: Economic feasibility is most frequently used technique.

For evaluating effectiveness of a proposed system more commonly known as cost benefit analysis, the procedure is to determine the benefit and saving that are expected from a proposed system and them with cost, a decision is taken to design and implement system otherwise further justification or alternative in the proposed system will have to be made if it is to have a chance of making improvement.

3) Operational Feasibility: It is mainly related to human organizational political aspects .The operational feasibility study is carried out by a small group of people who are familiar with information system techniques, which are relevant to the project and are skilled in system analysis and design process.

3.3 EXISTING SYSTEM:-

1) No proper income and expenditure detail.

2) No proper payment detail.

3) Time consuming.

4) No update information.

5) No security.

6) Redundancy

7) Accuracy

8) Information Retrieval

9) Generation of instantaneous reports not possible.

3.4 PROPOSED SYSTEM:-

In proposed system we can keep all the details and how much income he has getting into and what expenditure he has done. It is also helpful to take all the details for 1year which is very helpful to pay the tax. The above forms are input contains some data input and daily inputs. Apart from this we are mainly generating reports of master data and daily information to unless the performance of the operation.

1) Essential fields are not left blank.

2) Correct format.

3) Accuracy in data value.

4) Active speed.

5) Information of essential reports.

6) Security.

3.5 Limitations:

The main Limitations of existing system are:-

1) The existing system is maintained manually so there is a problem of errors in maintaining of records.

2) The existing system has the problem of providing security to its records.

3) The existing system consumes more time and manpower.

4) The existing system has the problem of storing of records.

5) Repetition of work.

CHAPTER-4

SYSTEM DESIGN

The most creative and challenging phase of the system life cycle is system design. The term design describes a final system and the process by which it is developed. It refers to the technical specification that will be applied in implementing the candidate system.

The main step in design is to determine how the output to be produced and in what format.

Samples of the output (and input) are also presented. Input data and master files have to be designed to meet the requirement of the proposed output. System design is detailed concentration on the technical and other specifications that will make the new system operational.

System Design is multistep process that focuses on the data structure software architecture procedural detail and interface between the models. The design process also translates the requirements into the representation of the software that can be accessed for quality before coding begins.

Computer software design is relatively easily in its evaluation. Therefore, software methodology lacks the dependent flexibility and quantitative nature that is normally associated with classical engineering design disciplines.

System design goes through three phases of development:-

1. Logical Design

2. Physical Design

3. Structural Design

1. Logical Design:-

Logical design describes the inputs outputs databases and procedural all in a format that meets user requirements.

When analyst prepares the logical system design, they specify the user needs at a level of details that virtually determines the information flow into and out of the system and the required data resources.

2. Physical System Design:-

Physical design produces the working system by defining the design specifications that tell the programmers exactly what the candidate system must do. In turn, the programmer writes the necessary programs or modifies the software package that accepts input from the user, performs the necessary calculations through the existing file or data-base , produces the report on a hard copy or displays it on the screen, and maintains an updated data base at all the times.

3. Structural Design:-

Structured design is a data-flow-based methodology. The approach begins with a system specification that identifies input and outputs and describes the functional aspects of the system. The system specifications then are used as a basis for the graphic representation- data flow diagram (DFD). From the DFD, the next step is the definition of modules and their relationships to one another in a form called a structure chart, using a data dictionary and other structured tools.

CHAPTER-5

SYSTEM IMPLEMENTATION

5.1 SOFTWARE TESTING

This software product consist modules, Cultivation, Inventions, Marketing and reports. All 3 modules have finite number of functions, for all modules unit testing was carried out. Some errors were detected in the function, which were solved efficiently. System testing was followed by this specific set of data that was selected for the testing, with each test, test reports were generated indicating the behavior of each unit.

TEST CASE DETAILS

Test case Result

· When character is Please enter number

Entered in a number

Field

· When any data is Please fill all records

Left blank

· When no record is there No record left to delete

UNIT TESTING

Unit testing is nothing but testing each module with both valid and invalid data. Appropriate message will be displayed for invalid test case and result is produced for the valid ones. Later individual functions were used put together and made to behave properly gaining exact results.

Unit testing is the most important testing when considered with other forms of testing.

INTEGRATED TESTING

After completing all sorts of test cases on all the forms they all are integrated to form the result. This integrated testing was done with the sample data .The need for performing a integrated testing is to find the overall performance of the system.

BLACK BOX TESTING

Black box testing is done in order to some of the following types of errors

· Missing functions or an incorrect function.

· Interface error.

· Error in the external database access.

· Performance error

· Initialization error and

· Termination error.

WHITE BOX TESTING

White box testing is another type of testing technique used to find errors in a application, using this white box testing the following test cases were successfully tested to this project

· Checking weather all independent paths within the module have been exercised at least once or not

· All conditions are executing or not

· Exercise internal data structure to ensure their validity

· All possible validity checks are given or not.

SYSTEM TESTING

All the units of all modules are put together; a combination of the previous test cases was made as the input and the result were tested for completeness .a similar set of activities was performed by putting units of different forms together, different strategies were tried out and all the communications were tested successfully.

5.2 METHODOLOGY

Here the linear ordering of these activities is critical. End of the phase and the output of one phase is the input of other phase. The output of each phase is to be consistent with the overall requirement of the system. Some of the qualities of spiral model are also incorporated like after the people concerned with the project review completion of each of the phase the work done.

WATER FALL MODEL was being chosen because all requirements were known beforehand and the objective of our software development is the computerization /automation of an already existing manual working system.

5.3 CODING

Coding For Income

Imports System.Data.OleDb

Public Class frmIncome

Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)

If disposing Then

If Not (components Is Nothing) Then

components.Dispose()

End If

MyBase.Dispose(disposing)

End Sub

'Required by the Windows Form Designer

Private components As System.ComponentModel.IContainer

'Label1

Me.Label1.AutoSize = True

Me.Label1.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label1.Location = New System.Drawing.Point(23, 24)

Me.Label1.Name = "Label1"

Me.Label1.Size = New System.Drawing.Size(40, 19)

Me.Label1.TabIndex = 1

Me.Label1.Text = "Date"

'dtpDate

Me.dtpDate.CustomFormat = "dd-MMM-yyyy"

Me.dtpDate.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.dtpDate.Format = System.Windows.Forms.DateTimePickerFormat.Custom

Me.dtpDate.Location = New System.Drawing.Point(130, 24)

Me.dtpDate.Name = "dtpDate"

Me.dtpDate.Size = New System.Drawing.Size(141, 23)

Me.dtpDate.TabIndex = 2

'Label2

Me.Label2.AutoSize = True

Me.Label2.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label2.Location = New System.Drawing.Point(23, 56)

Me.Label2.Name = "Label2"

Me.Label2.Size = New System.Drawing.Size(57, 19)

Me.Label2.TabIndex = 3

Me.Label2.Text = "Source"

'cmbSource

Me.cmbSource.DropDownStyle = System.Windows.Forms.ComboBoxStyle.DropDownList

Me.cmbSource.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.cmbSource.Items.AddRange(New Object() {"Salary", "Business", "Interest", "Rental", "Agriculture"})

Me.cmbSource.Location = New System.Drawing.Point(130, 56)

Me.cmbSource.Name = "cmbSource"

Me.cmbSource.Size = New System.Drawing.Size(209, 24)

Me.cmbSource.TabIndex = 4

'Label3

Me.Label3.AutoSize = True

Me.Label3.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label3.Location = New System.Drawing.Point(23, 90)

Me.Label3.Name = "Label3"

Me.Label3.Size = New System.Drawing.Size(91, 19)

Me.Label3.TabIndex = 5

Me.Label3.Text = "Description"

'txtDes

Me.txtDes.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.txtDes.Location = New System.Drawing.Point(130, 95)

Me.txtDes.Multiline = True

Me.txtDes.Name = "txtDes"

Me.txtDes.Size = New System.Drawing.Size(261, 59)

Me.txtDes.TabIndex = 6

Me.txtDes.Text = ""

'Label4

Me.Label4.AutoSize = True

Me.Label4.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.Label4.Location = New System.Drawing.Point(23, 175)

Me.Label4.Name = "Label4"

Me.Label4.Size = New System.Drawing.Size(64, 19)

Me.Label4.TabIndex = 7

Me.Label4.Text = "Amount"

'txtAmount

Me.txtAmount.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.txtAmount.Location = New System.Drawing.Point(130, 173)

Me.txtAmount.Name = "txtAmount"

Me.txtAmount.TabIndex = 8

Me.txtAmount.Text = ""

'btnExit

Me.btnExit.DialogResult = System.Windows.Forms.DialogResult.Cancel

Me.btnExit.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.btnExit.Location = New System.Drawing.Point(255, 226)

Me.btnExit.Name = "btnExit"

Me.btnExit.TabIndex = 10

Me.btnExit.Text = "&Exit"

'btnAdd

Me.btnAdd.Font = New System.Drawing.Font("Verdana", 9.75!, System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, CType(0, Byte))

Me.btnAdd.Location = New System.Drawing.Point(118, 226)

Coding For Expenditure

Imports System.Data.OleDb

Public Class frmExpenditure

Inherits System.Windows.Forms.Form

#Region " Windows Form Designer generated code "

Public Sub New()

MyBase.New()

'This call is required by the Windows Form Designer.

InitializeComponent()

'Add any initialization after the InitializeComponent() call

End Sub

'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)

If disposing Then

If Not (components Is Nothing) Then

components.Dispose()

End If

MyBase.Dispose(disposing)

End Sub

Friend WithEvents btnExit As System.Windows.Forms.Button

Friend WithEvents btnAdd As System.Windows.Forms.Button

Friend WithEvents txtAmount As System.Windows.Forms.TextBox

<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()

Customer Details

Imports System

Imports System.Data

Imports System.Data.SqlClient

Public Class custmeddet

Private Sub custmedretdet_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim da1 As New SqlDataAdapter("select * from re", con)

Dim ds1 As New DataSet

da1.Fill(ds1)

dataGrid1.Refresh()

dataGrid1.DataSource = ds1.Tables(0)

End Sub

Private Sub textBox1_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles textBox1.TextChanged

Try

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim ds2 As New DataSet

Dim da2 As New SqlDataAdapter("select * from re where [billno] like '%" & textBox1.Text & "%'", con)

da2.Fill(ds2)

dataGrid1.DataSource = ds2.Tables(0)

Catch ex As Exception

MsgBox(ex.Message)

End Try

End Sub

Private Sub button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles button1.Click

Try

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim cm As New SqlCommand

cm.Connection = con

cm.Connection.Open()

Dim da2 As New SqlDataAdapter

Dim ds2 As New DataSet

da2 = New SqlDataAdapter("select * from re ", con)

da2.Fill(ds2)

If ds2.Tables(0).Rows.Count < 1 Then

MsgBox("No more customer returns are in the list")

ElseIf MsgBox("Are You Sure Delete the all customer return Details?", MsgBoxStyle.YesNo) = MsgBoxResult.Yes Then

cm.CommandText = "delete from re"

cm.ExecuteNonQuery()

End If

'refresh

Dim ds As New DataSet

Dim da As New SqlDataAdapter("select * from re", con)

da.Fill(ds)

dataGrid1.DataSource = ds.Tables(0)

Catch ex As Exception

MsgBox(ex.Message)

End Try

End Sub

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

Me.Close()

End Sub

End Class

Supplier

Imports System.Data.SqlClient

Public Class supplier

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Private Sub supplier_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

Dim da1 As New SqlDataAdapter

Dim ds1 As New DataSet

da1 = New SqlDataAdapter("select * from supplier", con)

da1.Fill(ds1)

Label11.Text = Format(Now, "dd/MM/yyyy")

dataGrid1.DataSource = ds1.Tables(0)

End Sub

Private Sub Buttonsave_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Buttonsave.Click

Try

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim cm As New SqlCommand

cm.Connection = con

cm.Connection.Open()

Dim da1 As New SqlDataAdapter

Dim ds1 As New DataSet

da1 = New SqlDataAdapter("select * from supplier ", con)

da1.Fill(ds1)

If (txtsupid.Text = 0) Then

MsgBox("Enter the Supplier ID Number other than Zero")

txtsupid.Focus()

ElseIf txtsupid.Text = "" Then

MsgBox("Enter the Supplier ID")

txtsupid.Focus()

ElseIf txtsupname.Text = "" Then

MsgBox("Enter the Supplier Name")

txtsupname.Focus()

ElseIf txtcompname.Text = "" Then

MsgBox("Enter the Company Name")

txtcompname.Focus()

ElseIf txtphone.Text = "" Then

MsgBox("Enter the Valid Phone Number")

txtphone.Focus()

ElseIf txtfax.Text = "" Then

MsgBox("Enter the Valid Fax Number")

txtfax.Focus()

End If

For i As Integer = 0 To ds1.Tables(0).Rows.Count - 1

If (txtsupid.Text = Val(ds1.Tables(0).Rows(i)("Supplier ID"))) Then

MsgBox("Enter Supplier ID other than used")

txtsupid.Focus()

Exit Sub

End If

cm.CommandText = "Insert into supplier values('" & txtsupid.Text & "','" & txtsupname.Text & "', '" & txtcompname.Text & "','" & txtphone.Text & "','" & txtfax.Text & "')"

cm.ExecuteNonQuery()

MsgBox("Added Successfully")

txtsupid.Text = ""

txtsupname.Text = ""

txtcompname.Text = ""

txtphone.Text = ""

txtfax.Text = ""

Dim da2 As New SqlDataAdapter

Dim ds2 As New DataSet

da2 = New SqlDataAdapter("select * from supplier", con)

da2.Fill(ds2)

dataGrid1.DataSource = ds2.Tables(0)

Catch ex As Exception

MsgBox(ex.Message)

End Try

txtsupid.Focus()

End Sub

Private Sub Button8_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button8.Click

Try

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim cm As New SqlCommand

Dim da2 As New SqlDataAdapter

Dim ds2 As New DataSet

cm.Connection = con

cm.Connection.Open()

If txtsupid.Text = "" Then

MsgBox("Enter the Supplier ID")

txtsupid.Focus()

ElseIf txtsupname.Text = "" Then

MsgBox("Enter the Supplier Name")

txtsupname.Focus()

ElseIf txtcompname.Text = "" Then

MsgBox("Enter the Company Name")

txtcompname.Focus()

ElseIf txtphone.Text = "" Then

MsgBox("Enter the Valid Phone Number")

txtphone.Focus()

ElseIf txtfax.Text = "" Then

MsgBox("Enter the Valid Fax Number")

txtfax.Focus()

Else

da2 = New SqlDataAdapter("select * from supplier where [Supplier ID]='" & txtsupid.Text & "'", con)

da2.Fill(ds2)

If ds2.Tables(0).Rows.Count < 1 Then

MsgBox("Invalid Supplier ID number")

Else

Dim da3 As New SqlDataAdapter

Dim ds3 As New DataSet

da3 = New SqlDataAdapter("select * from supplier where [Supplier ID]='" & txtsupid.Text & "'", con)

da3.Fill(ds3)

cm.CommandText = "Update supplier set [Supplier ID]='" & txtsupid.Text & "',[Supplier Name]='" & txtsupname.Text & "',[Company Name]='" & txtcompname.Text & "',[Phone Number]='" & txtphone.Text & "',[Fax Number]='" & txtfax.Text & "' where [Supplier ID]='" & txtsupid.Text & "'"

cm.ExecuteNonQuery()

MsgBox("Updated Successfully.")

txtsupid.Text = ""

txtsupname.Text = ""

txtcompname.Text = ""

txtphone.Text = ""

txtfax.Text = ""

Dim da4 As New SqlDataAdapter

Dim ds4 As New DataSet

da4 = New SqlDataAdapter("select * from supplier", con)

da4.Fill(ds4)

dataGrid1.DataSource = ds4.Tables(0)

End If

txtsupid.Enabled = True

txtsupname.Enabled = True

txtcompname.Enabled = True

txtsupid.Focus()

Catch ex As Exception

MsgBox(ex.Message)

End Try

End Sub

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

Try

Dim da1 As New SqlDataAdapter

Dim ds1 As New DataSet

da1 = New SqlDataAdapter("select * from supplier where [Supplier ID]='" & txtsupid.Text & "'", con)

da1.Fill(ds1)

If ds1.Tables(0).Rows.Count < 1 Then

MsgBox("Invalid Supplier ID Number")

Else

txtsupid.Text = Trim(ds1.Tables(0).Rows(0)(0))

txtsupname.Text = Trim(ds1.Tables(0).Rows(0)(1))

txtcompname.Text = Trim(ds1.Tables(0).Rows(0)(2))

txtphone.Text = Trim(ds1.Tables(0).Rows(0)(3))

txtfax.Text = Trim(ds1.Tables(0).Rows(0)(4))

txtsupid.Enabled = False

txtsupname.Enabled = False

txtcompname.Enabled = False

End If

Catch ex As Exception

MsgBox(ex.Message)

End Try

txtsupname.Focus()

End Sub

Private Sub Button9_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button9.Click

Try

Dim con As New SqlConnection("Initial Catalog=stock;Data Source=SAN\SQLEXPRESS;Integrated security =true")

Dim da2 As New SqlDataAdapter

Dim da1 As New SqlDataAdapter

Dim ds1 As New DataSet

Dim ds2 As New DataSet

Dim cm As New SqlCommand

cm.Connection = con

cm.Connection.Open()

da1 = New SqlDataAdapter("select * from supplier ", con)

da1.Fill(ds1)

If ds1.Tables(0).Rows.Count < 1 Then

MsgBox("No more Suppliers are in the list")

txtsupid.Focus()

ElseIf MsgBox("Are You Sure Delete Supplier Details ?", MsgBoxStyle.YesNo) = MsgBoxResult.Yes Then

cm.CommandText = "Delete from supplier where [Supplier ID]= '" & txtsupid.Text & "'"

cm.ExecuteNonQuery()

MsgBox("Successfully Deleted")

txtsupid.Text = ""

txtsupname.Text = ""

txtcompname.Text = ""

txtphone.Text = ""

txtfax.Text = ""

txtsupid.Focus()

End If

Dim da3 As New SqlDataAdapter

Dim ds3 As New DataSet

da3 = New SqlDataAdapter("select * from supplier", con)

da3.Fill(ds3)

dataGrid1.DataSource = ds3.Tables(0)

Catch ex As Exception

MsgBox(ex.Message)

End Try

End Sub

Private Sub Buttonclear_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Buttonclear.Click

txtsupid.Enabled = True

txtsupname.Enabled = True

txtcompname.Enabled = True

txtsupid.Text = ""

txtsupname.Text = ""

txtcompname.Text = ""

txtphone.Text = ""

txtfax.Text = ""

txtsupid.Focus()

End Sub

Private Sub ButtonClose_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ButtonClose.Click

adminmain.Show()

Me.Close()

End Sub

End Class

CHAPTER-6

CONCLUSION

The Main benefits are

· User friendly easy maintenance

· Easy way of transmitting information

· Provides user with well structured information

· Reduce manual work

· Saves time and effort

· Less man power

BIBLIOGRAPHY

The following books were referred during the analysis and execution phase of the project

ORACLE 8I THE COMPLETE REFERENCE

By Oracle Press

SQL FOR PROFESSIONALS

By Jain

VISUAL BASIC.NET Black Book

By Evangeleous Petersons

MSDN 2002

By Microsoft

Search This Blog

LM World

Medical Shop Management System

Overview of the .NET Framework:-

Features of the Common Language Runtime:-

.NET Framework Class Library

Client Application Development:-

Server Application Development:-

Introduction to Windows Forms (Visual Basic.NET):-

What Is a Form?

Coding For Income

Coding For Expenditure

Comments

Post a Comment

Popular posts from this blog

Chemical test for Tragacanth

Chemical test for Benzoin

Chemical test for Agar/Agar-Agar / Japaneese Isinglass