Sie sind auf Seite 1von 51

1.

INTRODUCTION

The Pharmacy management system is an application, which involves administrational functional, related to various details like stock maintenance, sales list, purchase list, billing list etc. Realizing the need for quick retrieval and easy management of data, the system was studied in depth, analyzed and computerized. Owing to the number of drawbacks evident in the e isting system, an automated solution is our pro!ect. "t aims to remove most of the drawbacks found e tensively in the e isting system. The P# is aimed to simply the comple and redundant process. This pro!ect being developed as a replacement for the e isting system is a graphical user interface with good interactions with the database.

2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
The client uses $# % cel, and maintains their records, however it is not possible them to share the data from multiple system in multi user environment, there is lot of duplicate work, and chance of mistake. &hen the records are changed they need to update each and every e cel file. There is no option to find and print previous saved records. There is no security' anybody can access any report and sensitive data, also no reports to summary report. Limitations of Existing Syst m

The e isting system only provides te t(based interface, which is not as user(friendly as )raphical user "nterface. #ince the system is implemented in $anual, so the response is very slow. The transactions are e ecuted in off(line mode, hence on(line data capture and modification is not possible.

Off(line reports cannot be generated due to batch mode e ecution.

2.2 !RO!OSED SYSTEM


There is a need of reformation of the system with more advantages and fle ibility. The Pharmacy $anagement #ystem eliminates most of the limitations of the e isting software.

2." O#$ECTI%ES &OR T'E !RO!OSED SYSTEM


EN'ANCEMENT( The main ob!ective of Pharmacy $anagement #ystem is to enhance and upgrade the e isting system by increasing its efficiency and effectiveness. The software improves the working methods by replacing the e isting manual system with the computer(based system.

AUTOMATION( The Pharmacy $anagement #ystem automates each and every activity of the manual system and increases its throughput. Thus the response time of the system is very less and it works very fast.

ACCURACY( The Pharmacy $anagement #ystem provides the uses a quick response with very accurate information regarding the users etc. *ny details or system in an accurate manner, as and when required.

USER)&RIENDLY(

The software Pharmacy $anagement #ystem has a very user(friendly interface. Thus the users will feel very easy to work on it. The software provides accuracy along with a pleasant interface. $ake the present manual system more interactive, speedy and user friendly.

A%AILA#ILITY( The transaction reports of the system can be retried as and when required. Thus, there is no delay in the availability of any information, whatever needed, can be captured very quickly and easily.

MAINTENANCE COST( Reduce the cost of maintenance.

2.* &EASI#ILITY STUDY

+. Technical ,easibility -. %conomical ,easibility .. Operational ,easibility.

1. T +,ni+a- & asi.i-ity The pro!ect entitles /0ourier #ervice #ystem1 is technically feasibility because of the below mentioned feature. The pro!ect was developed in 2ava which )raphical 3ser "nterface.

"t provides the high level of reliability, availability and compatibility. *ll these make 2ava an appropriate language for this pro!ect. Thus the e isting software 2ava is a powerful language. 2. E+onomi+a- & asi.i-ity

The computerized system will help in automate the selection leading the profits and details of the organization. &ith this software, the machine and manpower utilization are e pected to go up by 45(657 appro imately. The costs incurred of not creating the system are set to be great, because precious time can be wanted by manually. ". O/ 0ationa- & asi.i-ity "n this pro!ect, the management will know the details of each pro!ect where he may be presented and the data will be maintained as decentralized and if any inquires for that particular contract can be known as per their requirements and necessaries.

". SYSTEM S!ECI&ICATIONS

".1'ARD1ARE S!ECI&ICATION
Processor8 Pentium -.. $9z Ram8 .- $: 9ard disk8 -.+): ,loppy ;rive8 +.<< $: =eyboard8 +5> standard

".2 SO&T1ARE S!ECI&ICATION


Operating Platform8 &indows ?P ,rontend Tool8 @isual :asic :ackend Tool8 $icrosoft *ccess

"." LANGUAGE S!ECI&ICATION


Mi+0osoft %is2a- #asi+ 3.4 5&0ont)En67(

To develop any system along with the back(end tools which provide access to the database and also solves the database queries like oracle, to make a system interactive with the user the use of front(end tools comes into the picture. The front(end tools make the user interface with the system easier and also provide a user(friendly environment to the system. This rich language enables you to develop many different types of applications. Aou can create you can create programs that intersect with the hardware. "t is a programming language used to create window base application. @isual :asic is an old :*#"0 B:eginners *ll(purpose #ymbolic instruction codeC language. "t makes it very easy to get the user interface portion of your application up and running. 9undreds of functions and latest technological advances have been added to the language to make it an industrial D strength development environment suitable for almost my type of windows application. This is especially true with the advent of internet programming and ob!ect oriented programming. $icrosoft @isual :asic E.5 is one of the front(end tool provided by $icrosoft "nc. $icrosoft @isual :asic E.5 provides a fast way to develop applications for $icrosoft &indows. *s a front(end tool $icrosoft @isual :asic E.5 provides the ).3." interface to the user and it is supposed to be one of the beast front(end tools used today. Som of t, main f at20 s of %is2a- #asi+ 3.4 a0 -ist 6 . -o8( ;ata *ccess features allows you to create database and front(end applications for most popular database formats, including $icrosoft #FG #erver, Oracle, $icrosoft *ccess and other enterprise level database. "t includes a )3" environment for making windows based applications. *ctive ? technology allows you to use the functionality provided by other application such as $# &ord, $# % cel and other &indows applications. Aou can even automate applications and professional or enterprise editions of @isual :asic. "nternet capabilities make it easy to provide access to documents and applications across the internet from within your application.

"t provides a vital link to graphical environment and allows you to develop applications based on standard &indows features8 ;ialog :o es, 0ommand buttons, ;rop down menus, #croll bars, #election lists etc. "t also allows creating robust applications that fully make use of the graphical user interface. * multitude of wizards and other graphical tools aid developers new to @isual :asic. *;O(compliant data(bound controls. 9ierarchical record sets and the ,le )rid 0ontrol. @isual :asic is an event driven programming language. @isual :asic allows you to adopt more of parallel approach, with independent sections of code for each option that the user may select. This is known as %vent driven programming language. @isual data tools B@;T#C. *;O ;ata 0ontrol B*;O;0C. ;ata report design and ;ata form wizards. "t also helps the user with the #FG editor. :y connecting it with Oracle, #FG statements can be run and terminated through @isual :asic E.5. @isual :asic 0omponent creation. The language is very easy and it provides a very user friendly environment while programming in @isual :asic E.5. Packaging and ;eployment wizard. *llows for the creation of p(code and native code %?% files. p(code is a tokenized from of your source code that will be broken down at runtime into machine code, which is why @isual :asic will create this intermediately forms.

0an be e tended easily through the use of windows *P" calls, hundreds of third party controls and ;GGs, and integration with other windows applications through 0O$ and ;0O$. 9as a shorter learning curve and development time than 0H0II, ;elphi, and even Power :uilder. 3sed by most of the office suite tool as macro language. &ith the rest to follow. Other companies as well are starting to support @:* in their products, such as *uto0*;, @ision, 0orel;raw, #*P, and many others. *llows for rapid application development and is e cellent for business applications. 9as an e cellent integrated help facility and book online as well as it includes good debugging facilities and have many wizards that help automated repetitive tasks. Ob!ect(based development is possible using class modules and rapid application development BR*;C. *llows for the creation of 0O$ components such as *ctive ? controls, ;GGJs, and % ecJs. 0an integrate with the "nternet on both the server side and the client side. 0an create *ctive ? *utomation server. "ntegrates with $icrosoft transaction server. 0an run server either on the same machine or remotely on another computer. This allow for true distributed processing. AD%ANTAGES O& %ISUAL #ASIC 3.4( ;uring design time, it is possible to see how the program will look at the runtime. @isual :asic is very useful in designing and developing, effective and efficient windows based programs @: helps in making your program look quite effective and beautiful.

Aou can add menus, tool bars, status bars, te t bo es, etc. to blank window. "t is less time consuming and more user friendly. *lso user friendly programs can be developed very easily.

*. SYSTEM DESIGN

;esigning a system mainly focuses on the detailed implementation of the proposed system. "t emphasizes on translating performance specifications recorded at the time of system study into design specifications. &ILE DESIGN #ystem design phase is a transition from a user(oriented document to on the methods adopted for developing the system. ;esign part is the pivotal point in the system development life cycle. * dataflow(based approach, which is a structured design methodology, had been adopted. This approach begins with system specification that identifies inputs and outputs and describes the functional aspects of the system. DESIGN O#$ECTI%ES(

The system analyst must have clear understanding of the ob!ectives that the design is aiming to fulfill. There is usually more than one way of achieving a desired set of results. The acceptable design is likely to be a compromise between a numbers of factors. Particularly cost, reliability, accuracy, security, control, integration, e pandability, availability, and acceptability. The elegant design achieves its ob!ectives with minimum use or resources. IN!UT DESIGN @ery careful attention had to be given to input design, which is a ma!or part of the overall system design. "n order to make the data entry as easy, logical and error free as possible, specific standards had been followed. @alidation checks, provided in the system prevented the user in entering incorrect, erroneous data. This made sure that, only valid data had been available for data processing. "f valid data was entered, then meaningful error messages had been prompted to enter correct data. The interactive screen formats facilitate the entry of valid data.

%ALIDATIONS( #ome fields are having only number, as an "HP. ,or this key *#0"" is checked. "f they entered characters, it would display the message to enter number only. % change rates field will be validated for number and dot symbols. IN!UT DESIGN O#$ECTI%ES( The numbers of clear ob!ectives of input design are, To produce a cost effective method of input To achieve the highest possible level of accuracy To ensure that the input is acceptable to and understand by the user staff

IN!UT TY!E( % ternal, which is the prime input for the system

"nternal, which is user communication with the system. Operational, which is the computer departmentJs communication with the system. 0omputerized, which are inputs in the computer media coming from other internal systems.

"nteractive, which are inputs entered during a dialogue, with the computer.

T'E NATURE O& IN!UT !ROCESSING( ,le ibility and thoroughness of validation rules. 9andling of priorities within the input procedures. 3se of composite input documents to reduce the number odd ones #cheduling of input runs in case of large re!ection rates at validation

OUT!UT DESIGN( Output, as you probably know, generally refers to the results and information that are generated by the system. ,or many end(users, output is the main reason for developing the system and the basis on which they will evaluate the usefulness of the application. $ost end(users will not actually operate the information system or enter data through workstations, but they will use the output from the system. &hen designing output, systems analysts must accomplish the following. ;etermine what information to present ;ecide whether to display, print, or Kspeak1 the information and select the output medium. *rrange the presentation of information in an acceptable format. ;ecide how to distribute the output to intended recipients.

That alignment of information on a display or printed document is termed as layout. *ccomplishing the general activities listed above will require specific decisions, such as whether to use preprinted forms when preparing reports and documents, how many lines to plan on a printed page, or whether to use graphics and color. The output design is specified on layout performs, sheets that describe the location characteristics, and format of the column headings and pagination. *s we indicated at the beginning of this discussion, these elements are analogous to an architectJs blue print that shows the location of the each component.

CODE DESIGN The need to communicate with, and by means, of computers has made increasing demands on users to work with and understand computer codes instead of natural language. "t must always be remembered that, a code will be used by human beings, including, people who do not have much familiarity with data processing. 0odes should be designed with two features in mind8 optimum human(oriented use and machine efficiency.

DATA#ASE DESIGN
The general theme behind a database is to handle information as an integrated whole. * database is a collection of inter(related data stored with minimum redundancy to serve single users quickly and efficiently. The general ob!ective is to make information necessary, quick, ine pensive and fle ible for the user. Our database consists of employee details, reports to view the progress of the assigned task, activity of the employee and also about the pro!ect details, login information, "tem ;etail, #tock

;etail, #taff ;etail, etc. each table contains the related fields to store the details of the given entity. "n a database environment, through R;:$# is the software that provides the interface between the data files on the disk and the program that request the data. $icrosoft #FG #erver -555 is the R;:$#, which stores the table related to the proposed system.

*.2 NORMALI9ATION

"t is a process of converting a relation to a standard form. The process is used to handle the problems that can arise due to data redundancy i.e. repetition of data in the database, maintain data integrity as well as handling problems that can arise due to insertion, updating, deletion anomalies.

;ecomposing is the process of splitting relations into multiple relations to eliminate anomalies and maintain anomalies and maintain data integrity. To do this we use normal forms or rules for structuring relation.

Ins 0tion anoma-y8 "nability to add data to the database due to absence of other data.

D - tion anoma-y8 3nintended loss of data due to deletion of other data.

U/6at anoma-y8 ;ata inconsistency resulting from data redundancy and partial update

No0ma- &o0ms8 These are the rules for structuring relations that eliminate anomalies.

&IRST NORMAL &ORM8

* relation is said to be in first normal form if the values in the relation are atomic for every attribute in the relation. :y this we mean simply that no attribute value can be a set of values or, as it is sometimes e pressed, a repeating group.

SECOND NORMAL &ORM8

* relation is said to be in second Lormal form is it is in first normal form and it should satisfy any one of the following rules. 1) Primary key is a not a composite primary key

2) Lo non key attributes are present 3) %very non key attribute is fully functionally dependent on full set of primary key.

T'IRD NORMAL &ORM8 * relation is said to be in third normal form if their e its no transitive dependencies.

T0ansiti: D / n6 n+y8 "f two non key attributes depend on each other as well as on the primary key then they are said to be transitively dependent. The above normalization principles were applied to decompose the data in multiple tables thereby making the data to be maintained in a consistent state

*." DATA &LO1 DIAGRAM


DATA &LO1 DIAGRAM The data flow diagrams are pictorial or graphical representation of the outline of the system study. The data flow diagram covers all the processes and data storage area which takes place during any transaction in the system. The ;,; takes an input(process(output view of a system i.e. data ob!ects flow into the software, are transformed by processing elements, and resultant data ob!ects flow out of the software. ;ata ob!ects represented by labeled arrows and transformation are represented by circles also called as bubbles. ;,; is presented in a hierarchical fashion i.e. the first data flow model represents the system as a whole. #ubsequent ;,; refine the conte t diagram Blevel 5 ;,;C, providing increasing details with each subsequent level.

The ;,; enables the software engineer to develop models of the information domain M functional domain at the same time. *s the ;,; is refined into greater levels of details, the analysts perform an implicit functional decomposition of the system. *t the same time, the ;,; refinement results in a corresponding refinement of the data as it moves through the process that embodies the applications. * conte t(level ;,; for the system the primary e ternal entities produce information for use by the system and consume information generated by the system. The labeled arrow represents data ob!ects or ob!ect hierarchy.

RULES &OR D&D ,i the scope of the system by means of conte t diagrams. Organize the ;,; so that the main sequence of the actions Reads left to right and top to bottom.

"dentify all inputs and outputs. "dentify and label each process internal to the system with Rounded circles. * process is required for all the data transformation and Transfers. Therefore, never connect a data store to a data #ource or the destinations or another data store with !ust a ;ata flow arrow. ;o not indicate hardware and ignore control information. $ake sure the names of the processes accurately convey everything the process is done. There must not be unnamed process. "ndicate e ternal sources and destinations of the data, with Lumber each occurrence of repeated e ternal entities. "dentify all data flows for each process step, e cept simple Record retrievals. Gabel data flow on each arrow. 3se details flow on each arrow. #quares.

3se the details flow arrow to indicate data movements. !URC'ASE

SALES "t gives details about the sales of product. The sales details view shows the entire sales item and also update the stock in the stock. "t gives the detail of customer.

RE!ORTS "t shows the report of all transaction for particular period.

#ymbols used in ;,;s8 +. !0o+ ss( 9ere flow of data is transformed. e.g. Purchase of currencies, update inventory file, etc.

-. Ext 0na- Entity( * source or destination of data which is e ternal to the system. e.g. Public, ;ealer etc.

.. A 6ata f-o8( "t is packet of data. "t may be in the form of document, letter etc.

<.Data sto0 (*ny store data but with no reference to the physical method of storing.

*.* E)R Diag0ams The %ntity(Relationship B%RC model was originally proposed by Peter in +6NE O0henNEP as a way to unify the network and relational database views. #imply stated the %R model is a conceptual data model that views the real world as entities and relationships. * basic component of the model is the %ntity(Relationship diagram which is used to visually represents data ob!ects. #ince 0hen wrote his paper the model has been e tended and today it is commonly used for database design ,or the database designer, the utility of the %R model is8

it maps well to the relational model. The constructs used in the %R model can easily be transformed into relational tables. it is simple and easy to understand with a minimum of training. Therefore, the model can be used by the database designer to communicate the design to the end user.

"n addition, the model can be used as a design plan by the database developer to implement a data model in specific database management software.

Conn +ti:ity an6 Ca06ina-ity The basic types of connectivity for relations are8 one(to(one, one(to(many, and many(to(many. * one-to-one B+8+C relationship is when at most one instance of a entity * is associated with one instance of entity :. ,or e ample, /employees in the company are each

assigned their own office. ,or each employee there e ists a unique office and for each office there e ists a unique employee. * one(to(many B+8LC relationships is when for one instance of entity *, there are zero, one, or many instances of entity :, but for one instance of entity :, there is only one instance of entity *. *n e ample of a +8L relationships is * department has many employees %ach employee is assigned to one department * many-to-many B$8LC relationship, sometimes called non(specific, is when for one instance of entity *, there are zero, one, or many instances of entity : and for one instance of entity : there are zero, one, or many instances of entity *. The connectivity of a relationship describes the mapping of associated ER NOTATION There is no standard for representing data ob!ects in %R diagrams. %ach modeling methodology uses its own notation. The original notation used by 0hen is widely used in academics te ts and !ournals but rarely seen in either 0*#% tools or publications by non( academics. Today, there are a number of notations used, among the more common are :achman, crowQs foot, and ";%,"?. *ll notational styles represent entities as rectangular bo es and relationships as lines connecting bo es. %ach style uses a special set of symbols to represent the cardinality of a connection. The notation used in this document is from $artin. The symbols used for the basic %R constructs are8 Entiti s are represented by labeled rectangles. The label is the name of the entity. %ntity names should be singular nouns. R -ations,i/s are represented by a solid line connecting two entities. The name of the relationship is written above the line. Relationship names should be verbs

Att0i.2t s, when included, are listed inside the entity rectangle. *ttributes which are identifiers are underlined. *ttribute names should be singular nouns.

Ca06ina-ity of many is represented by a line ending in a crowQs foot. "f the crowQs foot is omitted, the cardinality is one.

Exist n+ is represented by placing a circle or a perpendicular bar on the line. $andatory e istence is shown by the bar Blooks like a +C ne t to the entity for an instance is required. Optional e istence is shown by placing a circle ne t to the entity that is optional

;. SYSTEM DE%ELO!MENT

;.1 Mo62- D s+0i/tion( +. Purchase -. #ales .. Report <. % it !20+,as Purchase details include about the products being purchased in the pharmacy. The admin can add new product id,product description and the amount and quantity of the particular product. Purchase details shows at what rate the products has been purchased from the dealer and dealer information. Sa- s The sales details contains about the sales information, and the sales data, the sales include how many medicine has been sale R /o0t The report is used to generates the details of Purchase details, sales details, and stock details. Exit This module is used to terminate the pro!ect.

3. SYSTEM TESTING AND IM!LEMENTATION 3.1 SYSTEM TESTING


Theoretically, a new designed system should have all the pieces in working order, but in reality, each piece works independently. Low is the time to put all pieces into one system and test it to determine whether it meets the userJs requirements. The purpose of the system is to consider all the likely variations to which it will be sub!ected and then push the system to its limits. "t is tedious but necessary step in system development. One needs to be familiar with the following basic terms. 3L"T T%#T"L)8 is testing changes made in an e isting or a new program. #%F3%LT"*G OR #%R"%# T%#T"L)8 is checking the logic of one or more programs in the candidate system, where the output of one program will affect the processing done by another program. #A#T%$ T%#T"L)8 is e ecuting a program to check logic changes made in it and with the intention of finding errors making the program fail. *00%PT*L0% T%#T"L)8 is running the system with live data by the actual user of the system. Testing is vital to the success of the system. #ystem testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. "n adequate testing or no(testing leads to errors that may not appear until months later. *nother reason for system testing is its utility as a user(oriented vehicle before implementation. The best program and the user have communication barriers due to different

backgrounds. The system tester Bdesigner, programmer, or userC who has developed some computer mastery can bridge this barrier.

Unit T sting( This focuses on the smallest unit of software design. The module using the details

design description as a guide' important control paths are tested to uncover errors within the boundary of the module. Unit t st +onsi6 0ation( The module interface id tested to ensure that information properly flows into and out of the program unit under test. The local data structures are e amined to ensure that the data stored temporarily maintains it integrity during all steps in an algorithm e ecution. :oundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing. The test of data flow across a module interface is required before any other test. "f data do not enter and e it properly, all other tests are moot. Unit !0o+ 620 ( 3nit test is normally considered ad!unct to the coding style. *fter source level code has been developed, reviewed and verified for correct synta , unit test case design begins. %ach test case should be coupled with a set of e pected results. Lormally, a driver is a Kmain program1 that accepts test case data, passes such data to the module to be tested and prints the relevant results. #tubs serve to replace modules that are subroutines called by the module to be tested. * #tub or

Rdummy stub programJ uses the subroutine moduleJs interface to do minimal data manipulation and returns. 3nit testing is simplified when a module with high cohesion is designed. &hen a module addresses only one function, the number of test cases is reduced and errors can be more easily predicted and uncovered. Int g0ation T sting( "ntegration is a systematic technique for constructing the program structure, while at the same time conducting tests to uncover errors associated with interfacing. The ob!ective is to make unit(tested modules and build a program structure that has been dictated by design. "ncremental integration is the program that is the program that is constructed and tested in small segments where errors are easier to isolate and correct. To/ 6o8n Int g0ation( Top(down integration is an incremental approach to the construction of program structure. $odules are integrated by moving downward through the control hierarchy, beginning with the main control module. $odule subroutine to the main control module is incorporated into the structure either in a depth(first manner is engaged for this system. :readth(first incorporates all modules directly subroutine at each level, moving across the structure horizontally. The integration process is performed in a series of five steps8 a. The main control module is used as a test driver and stubs are substituted for all modules directly subroutine to the main control module. .. ;epending on the integration approach selected Bdepth or breadth firstC subroutine stub are replaced one at a time with actual modules. +. Tests are conducted as each module is integrated.

6. On the completion of each set of test, another stub is replaced with the real module. . Registration testing is conducted to ensure that new errors have not been introduced. %a-i6ation t sting( *t the end of integration testing, the system is completely assembled as a package with interfacing errors corrected after which a final series of software tests namely validation testing begins. @alidation succeeds when the software functions in a manner that can be reasonably e pected by the user. C0it 0ia( #oftware validation is achieved through black bo conformity with requirements. Syst m T sting( #ystem testing is actually a series of different tests whose primary purpose is to fully e ercise the computer(based system. *lthough each test has a different purpose, all work should verify that all system elements have been properly integrated and perform allocated functions. :eing the most important test, the performance test is covered briefly below8 a. ! 0fo0man+ T sting8 ,or real(time systems, software that provides required function but does not conform to performance requirement is unacceptable. Performance testing is designed to test the run(time performance of software within the conte t of an integrated system. Performance testing occurs throughout all steps in the testing process. %ven at the unit level, the performance of an individual module may be accessed as tests are conducted. 9owever, it is not until all system elements are fully integrated that the true performance of a system can be ascertained. tests that demonstrate

3.2 SYSTEM IM!LEMENTATION

"mplementation is the stage where the theoretical design is turned into a working system. The most crucial stage in achieving a new successful system giving is confidence on the new system for the users that it will work efficiently and effectively.

The system can be implemented only after thorough testing is done and if it is found to work according to the specification.

"t involves careful planning, investigation of the current system and its constraints on implementation, design of methods to achieve the change over and an evaluation of change over methods a part from planning. Two ma!or tasks of preparing the implementation are education and training of the users and testing of the system.

The more comple of the system being implemented, the more involved will be the systems analysis and design effort required !ust for implementation.

The implementation phase comprises of several activities. The required hardware and software acquisition is carried out. The system may require some software to be developed. ,or

this, programs are written and tested. The user then changes over to his new fully tested system and the old system is discontinued

<. SCO!E &OR EN'ANCEMENT

This *pplication is designed to be generic as we develop our site we should take advantage of several areas in which you can improve and customize business.

*utomatic notification of newly placed orders to the companyJs shipping or processing department.

&e are trying to include different kinds of products, which are needed by the customer in their day to day life, and many more facilities for the customers.

0redit card facilities will be including for making the payment easy for the customer. #ervice charge will be there for credit cards.

*ddition of a procedure to verify the userJs credit card information.

=. CONCLUSION

The software KPharmacy $anagement #ystem1 has been developed in windows 64 environment using visual basic as front end and ms access as back end. Time consumptions reduced to a great e tent and user as less comple ity in handling this database.

The pro!ect is fully fledged and user friendly, %nd users will be lightened in using this software because it is easy to have bills and reports and mostly all contents to be entered are to selected from combo bo . This reduces the calculating efforts to be carried out by the users.

#I#LIOGRA!'Y

$#;L Gibrary $astering @isual :asic E BP%TRO3T#O#, :P: P3:G"0*"OL#C

0omplete reference to visual basic E B:P: PublicationsC

:eginner To Pro $urachJs @isual :asic E B2oel $urach, *nne Prince, :P: PublicationsC

Teach Aourself visual :asic E B#cott &arner, T*T* $c)raw 9"GG publicationsC

;atabase #ystem 0oncepts B9.,.=ORT9, $c)raw 9"GG PublicationsC

A!!ENDIX
A TA#LE DESIGN T*:G% L*$% 8 03#TO$%R

TA#LE NAME( MANU

TA#LE NAME( !TRAN

TA#LE NAME( !URRET

TA#LE NAME( SALESRET

TA#LE NAME( SALTRANS

TA#LE NAME( STOC>

#? SCREEN LAYOUTS

C? RE!ORT

D? SAM!LE CODING Private #ub 03S0lickBC ,ormE.#how %nd #ub

Private #ub ;*S0lickBC ;im d d T "nput:o B/%nter the "tem name/C ;ata%nvironment+.0ommand+ d ;ataReport+.#how %nd #ub

Private #ub ;*"S0lickBC ;im d d T "nput:o B/%nter the date from which u need/C ;ata%nvironment+.0ommand> d ;ataReport>.#how %nd #ub

Private #ub %?S0lickBC %nd

%nd #ub

Private #ub $S0lickBC ,orm..#how %nd #ub

Private #ub mnupdateS0lickBC ;im d d T "nput:o B/%nter the date from which u need/C ;ata%nvironment+.0ommand< d ;ataReport<.#how %nd #ub

Private #ub $OS0lickBC ;im d d T "nput:o B/%nter the medical code/C ;ata%nvironment+.0ommand. d ;ataReport..#how %nd #ub

Private #ub PRS0lickBC ,orm>.#how %nd #ub

Private #ub #RS0lickBC ,orm4.#how %nd #ub

Private #ub TRS0lickBC ,orm<.#how %nd #ub

Private #ub TR*S0lickBC ,ormN.#how %nd #ub

Private #ub &%S0lickBC ;im d d T "nput:o B/%nter the "tem code/C ;ata%nvironment+.0ommand- d ;ataReport-.#how

%nd #ub ;im ;: *s ;atabase, R#, R#+, R#-, R#. *s Recordset Private #ub 0ombo+SGost,ocusBC #et R#+ T ;:.OpenRecordsetB/#%G%0T U ,RO$ 03#TO$%R &9%R% 03#T0O;%T/ M @alB0ombo+.Te tCC Te t-.Te t T R#+B+C %nd #ub

Private #ub 0ombo-SGost,ocusBC #et R#. T ;:.OpenRecordsetB/#%G%0T U ,RO$ $*L3 &9%R% $%;0O;%T/ M @alB0ombo-.Te tCC Te t..Te t T R#.B+C %nd #ub

Private #ub 0ommand+S0lickBC ;"#*:G% 0ommand..%nabled T True 0ommand<.%nabled T True R#.*ddLew Option+.%nabled T True Option-.%nabled T True 0ombo+.%nabled T True

0ombo-.%nabled T True Option+.#et,ocus %nd #ub

Private #ub 0ommand-S0lickBC ;im = *s ;ouble R#B5C T Te t+.Te t "f Option+.@alue T True Then R#B+C T /0#/ %nd "f "f Option-.@alue T True Then R#B+C T /0R/ %nd "f R#B-C T 0ombo+.Te t R#B.C T 0ombo-.Te t R#B<C T Te t<.Te t R#B>C T Te t4.Te t R#.3pdate 0ommand-.%nabled T ,alse 0ommand..%nabled T ,alse 0ommand+.%nabled T True

0ommand+.#et,ocus #et R#- T ;:.OpenRecordsetB/#%G%0T U ,RO$ #TO0= &9%R% $%;0O;% T/ M @alB0ombo-.Te tCC R#-.%dit = T R#-B+C R#-B+C T = ( @alBTe t<.Te tC R#-.3pdate $sg:o /3R R%0OR; 9*# :%%L #*@%;/ "f R#-B+C V R#-B-C Then $sg:o /T9% #TO0= G%@%G "# :%GO& R%OR;%R G%@%G, PG%*#% OR;%R #TO0=/ %nd "f %nd #ub

Private #ub 0ommand.S0lickBC Option+.%nabled T ,alse Option-.%nabled T ,alse 0ombo+.%nabled T ,alse 0ombo-.%nabled T ,alse Te t-.Te t T // Te t..Te t T // Te t<.Te t T //

Te t>.Te t T // Te tE.Te t T // Te tN.Te t T // Te t4.Te t T // 0ommand..%nabled T ,alse 0ommand+.%nabled T True 0ommand+.#et,ocus

%nd #ub

Private #ub 0ommand<S0lickBC 3nload $e %nd #ub

Private #ub ,ormSGoadBC #et ;: T Open;atabaseB*pp.Path M /WR*$*.$;:/C #et R# T ;:.OpenRecordsetB/#*GTR*L#/C #et R#+ T ;:.OpenRecordsetB/03#TO$%R/C #et R#- T ;:.OpenRecordsetB/#TO0=/C #et R#. T ;:.OpenRecordsetB/$*L3/C "f R#+.Record0ount VX 5 Then

R#+.$ove,irst ;o &hile Lot BR#+.%O, T TrueC 0ombo+.*dd"tem R#+B5C R#+.$oveLe t Goop %lse 9";%*GG $sg:o /T9%R% *R% LO R%0OR;# "L T9% 03#TO$%R T*:G%/ %nd "f "f R#-.Record0ount VX 5 Then R#-.$ove,irst ;o &hile Lot BR#-.%O, T TrueC 0ombo-.*dd"tem R#-B5C R#-.$oveLe t Goop %lse 9";%*GG $sg:o /T9%R% *R% LO R%0OR;# "L $*L3,*0T3R% T*:G%/ %nd "f Option+.%nabled T ,alse Option-.%nabled T ,alse

0ombo+.%nabled T ,alse 0ombo-.%nabled T ,alse Te t+.Te t T ;ateY %nd #ub

Public #ub 9";%*GGBC G*:G%-.@isible T ,alse G*:G%..@isible T ,alse G*:G%<.@isible T ,alse G*:G%>.@isible T ,alse G*:G%E.@isible T ,alse G*:G%N.@isible T ,alse G*:G%4.@isible T ,alse G*:G%6.@isible T ,alse G*:G%+5.@isible T ,alse G*:G%++.@isible T ,alse G*:G%+-.@isible T ,alse Option+.@isible T ,alse Option-.@isible T ,alse Te t+.@isible T ,alse Te t-.@isible T ,alse

Te t..@isible T ,alse Te t<.@isible T ,alse Te t>.@isible T ,alse Te tE.@isible T ,alse Te tN.@isible T ,alse Te t4.@isible T ,alse 0ombo+.@isible T ,alse 0ombo-.@isible T ,alse 0ommand+.@isible T ,alse 0ommand-.@isible T ,alse 0ommand..@isible T ,alse %nd #ub

Public #ub %L*:G%BC 0ommand+.%nabled T True 0ommand-.%nabled T True 0ommand..%nabled T True 0ommand<.%nabled T True %nd #ub

Public #ub ;"#*:G%BC

0ommand+.%nabled T ,alse 0ommand-.%nabled T ,alse 0ommand..%nabled T ,alse 0ommand<.%nabled T ,alse %nd #ub

Private #ub Te t<SGost,ocusBC #et R#. T ;:.OpenRecordsetB/#%G%0T U ,RO$ $*L3 &9%R% $%;0O;%T/ M @alB0ombo-.Te tCC Te t>.Te t T R#.BEC Te tE.Te t T @alBTe t<.Te tC U @alBTe t>.Te tC "f Option+.@alue T True Then Te tN.Te t T @alBTe tE.Te tC Te t4.Te t T @alBTe tE.Te tC ( @alBTe tN.Te tC Te t4.%nabled T ,alse 0ommand-.%nabled T True 0ommand-.#et,ocus %nd "f "f Option-.@alue T True Then

Te tN.#et,ocus Te t4.%nabled T ,alse %nd "f

%nd #ub

Private #ub Te tNSGost,ocusBC

Te t4.Te t T @alBTe tE.Te tC ( @alBTe tN.Te tC Te t4.%nabled T ,alse 0ommand-.%nabled T True 0ommand-.#et,ocus %nd #ub