SYNOPSIS

The system entitled ORDER PROCESSING SYSTEM is windows application software which attempts to integrate all departments and functions across a company onto a single computer system that can serve all those departments particular needs. Each of those departments typically has its own computer system optimized for the particular ways that the department does its work. But this combines them all together into a single, integrated software program that runs off a single database so that the various departments can more easily share information and communicate with each other. This system vanquishes the old stand alone computer systems in manufacturing, dye house and warehouse and replaces them into a single unified software program divided into several modules that roughly appro imate the old standalone systems. !anufacturing, dye house and warehouse all still get their own software, e cept now the software is linked together so that finance can look into the warehouse software to see if an order has been shipped. This software is fle ible enough that the user can install some modules without buying the whole package.

"

ORGANIZATIONAL PROFILE

SRI RAMALAKSHMI TEX TECH Established in the year "#$%, &'( ')!)*)+&,!( TE-.TE/, is an organization driven by the core values of 01)*(T2, &E'3(/E and T'1&T. The founder, !r.4inesh +umar, is a professional manager, with previous e perience of more than % decades with big corporate groups., , E /, 4 / ! and the T)T)&, in the field of merchandise e port business, with te tiles being the area of e pertise. Evolving from an individual vision, today &'( ')!)*)+&,!( TE-.TE/, is a highly professional organization with a core set of people involved in its operations. The company has a broad customer base spread across continents5 )sia &candinavia Europe &outh )merica . 6apan . &weden . 7ermany, &pain . /hile, /olumbia The business at &'( ')!)*)+&,!( TE-.TE/, is handled by professionals in their respective field of operation. Every member of the organization is driven by the motto customer satisfaction through the entire spectrum of their performance. ) dedicated commercial team ensures customers of e cellent client servicing, while a professionally trained design and quality control team assures the clientele of high quality merchandise. The strategic tie.ups with manufacturing partners form an integral part of the team ensuring a steady supply of merchandise. Vision To be a vertically integrated apparel company focused on providing complete solutions to its customers, backed by quality service and an ethical code of conduct. Mission To achieve a productivity inde higher than 89:. To consistently maintain < ;.9 )0* in all shipments To strengthen employee welfare systems including setting up dormitory facilities for ;9<< workers ;

To increase infrastructure capabilities to ;<<< machines and thereby achieve the production capacity of "< million pieces Str n!t"s +nowledge partnership of +&) Technopak, a leading consultant in apparel manufacturing ,ighly dedicated team of professionals &cientifically recruited and perpetually trained human resources =no child labour> &trategically located, with pro imity to seaports and airports and logistically advantageous access to raw material sourcing centres /alm and serene, yet vibrant ambience which facilitates good work environment and practices &ocially and ethically responsible ownership and strong belief in participative management ?le ibility and versatility built into the shop floor for enhancing the efficiency and productivity &ignatory to ,(3@ )(4& Aolicy of /(( Equal Employment Aolicy practiced

#$ INTROD%CTION

#$# A&O%T THE SYSTEM ' The system entitled ORDER PROCESSING SYSTEM is Bindows application software which attempts to integrate all departments and functions across a lab into a single computer system that can serve all the departments need. Each department typically has its own computer system optimized for the particular work. But this system combines them into a single, integrated software program that runs a single database, which allows various departments easily share information and communicate with each other. The Aroposed &ystem vanquishes the old stand.alone computer systems in the lab and replaces them into a single unified software program divided into several modules that roughly appro imate the old standalone systems. This system contains the following modules5 Lo!in (or) This module is used to verify the correct user name and password. This allows only the authorized users to enter into the system and access the database. C*sto) r D t+i,s This module contains the customer details. (t includes the details like the customer id, customer name, address, area name, phone number, T(C CD, /&T Co. *ogin form /ustomer 4etails &upplier 4etails Aroduct 4etails )rea @sales 4etails (nvoice 4etails &tock 4etails

S*--,i r D t+i,s This module stores the supplier details. (t contains the supplier information such as the &upplier id, supplier name, address, phone number, tin number, /&T Co. Pro.*/t D t+i,s This module is used to store the products that are available in the store. (t stores the product information such as the Aroduct id, product name, product category, price, 1D!, supplier (d, supplier name, ta details. S+, s D t+i,s This module contains the sales no, sales date, customer name, total products sold, total amount. In0oi/ D t+i,s This module is used to store the bill details and generate the invoice. (t stores the details such as the (nvoice no, invoice data, party name, area name sales man name, description, quantity, ta amount. Sto/1 D t+i,s This module stores the stock details. (t contains the details such as the Aroduct id, Aroduct name, stock in hand2 category, no of items. #$3 O&4ECTIVE OF THE PRO4ECT ' The obFective of the proFect is to manage the resource to the full e tend. Or. r Pro/ ssin! S5st ) automates the tasks involved in performing a business processGsuch as order fulfillment, which involves taking an order from a customer, 4elivery it and (nvoice for it. There are three maFor reasons why companies undertake Drder Arocessing &ystem5 To integrate all the data across the company. To standardize manufacturing processes. amount, discount, generate, round off, total amount, net

 &tandardizing the processes and using a single, integrated computer system can save time, increase productivity and reduce headcount Aroperly implementing Drder Arocessing &ystem can give deliver a significant competitive advantage and helps the user to run the business more effectively, efficiently, and responsively.

#$6 EXISTING SYSTEM The maFor drawback in the e isting system is more time consumed in calculations and preparation of reports. 'eport preparation is a hectic task to be done, and data integrity is highly impossible. 'eports maintained manually causes many problem like report missing or any damage to the report causes problem in delivery of the product. LIMITATIONS OF EXISTING SYSTEM The drawbacks of the E isting systems are o Cotable not access the previous records of the transactions easily. o *ot of paper work is done. o !ore !ental and Ahysical efforts are needed. o &earching the record in the future will lead to physical tiredness it also lead to time consuming o )ccessing speed is less. o 'eport generation should be done with more human efforts. o Co security #$7 PROPOSED SYSTEM' The proposed system is introduced to overcome the above difficulties. This system fulfills the users needs. This system was designed to the user with many benefits. O&4ECTIVES OF THE SYSTEM Easy )ccess of records. To reduce the human burden. H

(t takes less time for searching information, about the company details Co need to strain to search the particular transaction number. (t reduces the cost for maintaining the reports. (t reduces the work of the staff in the company.

3$ SYSTEM ST%DY 3$# PRO&LEM IDENTIFICATION The primary necessity of the system was it must maintain all details of the /ompany. The system has to update the data entry. This system must keep track of bulk of data, carried out companys background information and their problems registered with the database. &ecurity and protection of data were another necessity. The overall system must be fast and convenient. ) large database is used for storing a large amount of data. This system brings the complete and innovative solution to meet with the company activities. Bhich is core to the officer satisfactionI (t provides the comprehensive services including development, deployment, integration, enhancement, migration, maintenance, documentation and training. The following checklist for (nput@Dutput 4escription should be completed after the initial requirements document is completed but before it is presented to the developers5 Or!+ni8+tion +n. Co)-, t n ss )re all internal cross.references to other requirements correctI )re all requirements written at a consistent and appropriate level of detailI 4o the requirements provide an adequate basis for designI (s the implementation priority of each requirement includedI )re all e ternal hardware, software, and communication interfaces definedI ,ave algorithms intrinsic to the functional requirements been definedI 4oes the &'& include all of the known customer or system needsI $

 (s any necessary information missing from a requirementI (f so, is it identified as TB4I (s the e pected behavior documented for all anticipated error conditionsI Corr /tn ss 4o any requirements conflict with or duplicate other requirementsI (s each requirement written in clear, concise, unambiguous languageI (s each requirement verifiable by testing, demonstration, review, or analysisI (s each requirement in scope for the proFectI (s each requirement free from content and grammatical errorsI /an all of the requirements be implemented within known constraintsI )re any specified error messages unique and meaningfulI 9*+,it5 Attri:*t s )re all performance obFectives properly specifiedI )re all security and safety considerations properly specifiedI )re other pertinent quality attribute goals e plicitly documented and quantified, with the acceptable tradeoffs specifiedI Tr+/ +:i,it5 (s each requirement uniquely and correctly identifiedI

 (s each software functional requirement traceable to a higher.level requirement =e.g., system requirement, use case>I S- /i+, Iss* s )re all requirements actually requirements, not design or implementation solutionsI )re the time.critical functions identified, and timing criteria specified for themI ,ave internationalization issues been adequately addressedI The business requirements describe the needs of the business. The following types of requirements must be defined fully here5

S /*rit5 R ;*ir ) nts G 4efine the security measures that must apply to this product as defined by the business unit and the &ecurity Aolicies and Arocedures 7uide.

P r(or)+n/ R ;*ir ) nts G 4efine the performance necessary in the product from a business perspective.

A0+i,+:i,it5 R ;*ir ) nts G 4efine the timeframes during which the product must be available to meet the needs of the business.

%s r R ;*ir ) nts J 4efine e actly what the business wants the finished product to look and function like.

3$3 HARD<ARE CONFIG%RATION Arocessor 5 (ntel 4ual /ore Arocessor

"<

Arocessor &peed !emory =')!> ,ard 4isk ?loppy 4rive !onitor !ouse

5 ".8 7,z 5 9"; !B 5 "< 7B 5 % K L".EE !B 4rive 5 *7 !onitor 5 (ntel Dptical !ouse

3$6 SOFT<ARE CONFIG%RATION Dperating &ystem ?ront End Tool Back End Tool 5 Bindows -A 5 !icrosoft 3isual Basic H.< 5 !icrosoft )ccess

""

6$ SYSTEM DESIGN &ystem design centers the software engineering and applied science regardless of the software process model that is used. Dnce the software requirements have been analyzed and specified, tests that are required in the building and verifying the software is done. Each activity transforms information in a number that ultimately results in validated computer software. There are mainly three characteristics that serve as guide for evaluation of good design, The design must implement all of e plicit requirements contained in the analysis model, and it must accommodate all of the implicit requirements desired by the customer. The design must be readable, understandable guide for those who generate code and for those who test and subsequently support the software. The design should provide a complete picture of software, addressing the data, its functional and behavioral domains from the implementation perspective. &ystem design is a process of planning a new system or to the complement of the e isting system. The design based on the limitations of the e isting system and the requirements specification gathered in the phase of system analysis.

";

In-*t . si!n is the process of converting the user.oriented description of the computer based business information into program.oriented specification. The goal of designing input data is to make the automation as easy and free from errors as possible. /ustomer 4etails &upplier 4etails Aroduct 4etails )rea @sales 4etails (nvoice 4etails &tock 4etails

Pro/ ss D si!n is the design of the process to be doneM it is the designing that leads to the coding. ,ere the conditions and the constraints given in the system are to be considered. )ccordingly the designing is to be done and processed. O*t-*t D si!n is the most important and direct source of information to the user. The output design is an ongoing activity during study phase. The obFectives of the output design define the contents and format of all documents and reports in an attractive and useful format. The main output generated here is the reports. The reports were generated for selective reasons. The various reports generated are as follows, /ustomer 4etails 'eport &upplier 4etails 'eport Aroduct 4etails 'eport )rea @sales 4etails 'eport (nvoice 4etails 'eport &tock 4etails 'eport

6$# SYSTEM METHODOLOGY 3B) is functionally rich and fle ible but it does have some important limitations, such as restricted support for function pointers which are used as callback functions in the Bindows )A(. (t has the ability to use =but not create> =)ctive-@/D!> 4**s, and later versions add support for class modules. "%

(t was also built into Dffice applications apart from version ;<<$ for )ppleNs !ac D& -, other !icrosoft applications such as !icrosoft !apAoint and !icrosoft 3isioM as well as being at least partially implemented in some other applications such as )uto/)4, BordAerfect, and )rc7(&. (t supersedes and e pands on the capabilities of earlier application.specific macro programming languages such as BordNs BordBasic, and can be used to control many aspects of the host application, including manipulating user interface features, such as menus and toolbars, and working with custom user forms or dialog bo es. 3B) can also be used to create import and e port filters for various file formats, such as D4?. )s its name suggests, 3B) is closely related to 3isual Basic and uses the 3isual Basic 'untime, but can normally only run code within a host application rather than as a standalone application. (t can, however, be used to control one application from another using D*E )utomation. ?or e ample, it is used to automatically create a Bord report from E cel data, in turn automatically collected by E cel from polled observation sensors. The 3B) (4E is reached from within an Dffice document by pressing the key sequence )ltO?"". Bhen write a 3isual Basic program, first have to design the user interface. Essentially, a 3isual Basic user interface consists of obFects that you place on the screen and arrange in some semblance of organization so that the screen looks pretty. The common elements of a 3isual Basic user interface appear in ?igure " and consist of the following5 ?orms =also known as windows> Buttons =such as command buttons and radio buttons> Bo es =such as te t bo es and check bo es> *abels Aictures =such as icons and graphics> 6$3 SOFT<ARE STR%CT%RE "E

PLATFORM= <INDO<S XP Bindows -A is a line of operating systems produced by !icrosoft for use on personal computers, including home and business desktops, notebook computers, and media centers. The name P-AP is short for Pe perienceP. Bindows -A is the successor to both Bindows ;<<< Arofessional and Bindows !e, and is the first consumer. oriented operating system produced by !icrosoft to be built on the Bindows CT kernel and architecture. Bindows -A was first released on ;9 Dctober ;<<", and over E<< million copies were in use in 6anuary ;<<H, according to an estimate in that month by an (4/ analyst. (t is succeeded by Bindows 3ista, which was released to volume license customers on $ Covember ;<<H and worldwide to the general public on %< 6anuary ;<<8. 4irect DE! and retail sales of Bindows -A ceased on %< 6une ;<<$, although it is still possible to obtain Bindows -A from &ystem Builders =smaller DE!s who sell assembled computers> until %" 6uly ;<<# or by purchasing Bindows 3ista 1ltimate or Business and then downgrading to Bindows -A.

LANG%AGE FRONT END > VIS%AL &ASIC Vis*+, &+si/ =V&> is the third.generation event.driven programming language and integrated development environment =(4E> from !icrosoft for its /D! programming model. 3isual Basic is relatively easy to learn and use.Q"RQ;R 3isual Basic was derived from B)&(/ and enables the rapid application development =')4> of graphical user interface =71(> applications, access to databases using 4ata )ccess DbFects, 'emote 4ata DbFects, or )ctive- 4ata DbFects, and creation of )ctive- controls and obFects. &cripting languages such as 3B) and 3B&cript are syntactically similar to 3isual Basic, but perform differently. Q%R

"9

) programmer can put together an application using the components provided with isual Basic itself. Arograms written in 3isual Basic can also use the Bindows )A(, but doing so requires e ternal function declarations. The final release was version H in "##$. !icrosoftNs e tended support ended in !arch ;<<$ and the designated successor was 3isual Basic .CET =now known simply as 3isual Basic>. &ACK END > MICROSOFT ACCESS !icrosoft released )ccess version ".< on "% Covember "##;, and an )ccess "." release in !ay "##% to improve compatibility with other !icrosoft products and include the )ccess Basic programming language. !icrosoft specified the minimum hardware requirements for )ccess v;.< as5 !icrosoft Bindows v%." with E !B of ')! required, H !B ')! recommendedM $ !B of available hard disk space required, "E !B hard disk space recommended. The product shipped on seven ".EE !B diskettes. The manual shows a "##% copyright date. Driginally, the software worked well with relatively small databases but testing showed that some circumstances caused data corruption. ?or e ample, file sizes over "< !B proved problematic =note that most hard disks held less than 9<< !B at the time this was in wide use>, and the Getting Started manual warns about a number of circumstances where obsolete device drivers or incorrect configurations can cause data loss. Bith the phasing out of Bindows #9, #$ and !E, improved network reliability, and !icrosoft having released $ service packs for the 6et 4atabase Engine, the reliability of )ccess databases has been improved and it supports both more data and a larger number of users. Bith Dffice #9, !icrosoft )ccess 8.< =a.k.a P)ccess #9P> became part of the !icrosoft Dffice Arofessional &uite, Foining !icrosoft E cel, Bord, and AowerAoint and transitioning from )ccess Basic to 3isual Basic for )pplications =3B)>. &ince then, !icrosoft has released new versions of !icrosoft )ccess with each release of "H

!icrosoft Dffice. This includes )ccess #8 =version $.<>, )ccess ;<<< =version #.<>, )ccess ;<<; =version "<.<>, )ccess ;<<% =version "".9>, )ccess ;<<8 =version ";.<>, and )ccess ;<"< =version "E.<>. The native )ccess database format =the 6et !4B 4atabase> has also evolved over the years. ?ormats include )ccess ".<, ".", ;.<, 8.<, #8, ;<<<, ;<<;, ;<<8, and ;<"<. The most significant transition was from the )ccess #8 to the )ccess ;<<< formatM which is not backward compatible with earlier versions of )ccess. )t the time of this writing, all newer versions of )ccess support the )ccess ;<<< format. Cew features were added to the )ccess ;<<; format which can be used by )ccess ;<<;, ;<<%, ;<<8, and ;<"<. (n )ccess ;<<8, a new database format was introduced5 )//4B. The )//4B supports comple data types such as multivalue and attachment fields. These new field types are essentially recordsets in fields and allow the storage of multiple values in one field. Bith )ccess ;<"<, a new version of the )//4B format supports hosting on a &hareAoint ;<"< server for e posure to the web. Arior to the introduction of )ccess, the desktop database market was dominated by Borland with their Aarado and dBase programs, and ?o Aro. !icrosoft )ccess was the first mass market database program for Bindows. Bith the purchase of ?o Aro and incorporating its 'ushmore query optimization routines into )ccess, !icrosoft )ccess quickly became the dominant database for Bindows effectively eliminating the competition which failed to transition from the !&.4D& world.Q;R )ccessNs initial codename was /ircussM the forms engine was called 'uby. This was before 3isual Basic . Bill 7ates saw the prototypes and decided that the B)&(/ language component should be co.developed as a separate e pandable application, a proFect called Thunder. The two proFects were developed separately as the underlying forms engines were incompatible with each otherM however, these were merged together again after 3B).

"8

)ccess was also the name of a communications program from !icrosoft, meant to compete with Aro/omm and other programs. This proved a failure and was dropped. 2ears later, !icrosoft reused the name for its database software.

6$7 CODING STYLE These are the 3isual Basic coding standards used by ?rez &ystems *imited. Arogrammers working for ?rez &ystems *imited are required to work to these standards unless a client has their own standards that they require to be adopted. These standards are being published on the web to help other programmers who may be in search of a starting point to their own set of coding standards. (f you decide to use these standards as your own or part of your own you should include an acknowledgement to ?rez &ystems *imited in the te t. 2ou are forbidden from publishing these standards in order to make a profit. Bhere the programmer decides to deviate form the standards this must be for a good reason that must be documented within the code as a comment. Bhere code is imported, for instance, from the 3isual Basic Bindows )A( 3iewer or from !&4C, it is CDT a requirement to change the code to reflect these standards. )lthough, where it is a sizeable piece of code, comments should be included stating that it is imported and from where it was imported. "$

These standards only apply to new work, it is not a requirement that they be applied to e isting code. NAMING CONVENTIONS Aroviding a standard for naming variables, constants, functions, controls and modules makes your proFects and code easier to follow by other programmers following the same standard.

VARIA&LE NAMING 3ariable names shall describe their use, shall be in mi ed case with an initial upper case character for each word, and shall have N,ungarianN prefi es that describe their type and scope. )bbreviations shall be avoided, but where they are used they are to be used consistently throughout the entire application. ,ungarian prefi es not only identify the type of a variable but also have the advantage of avoiding confusion between variables and functions, methods or properties. H*n!+ri+n T5- Pr (i? s' 4ata Type Arefi E ample Boolean b b(s3alid Byte byt byt)ge /urrency cur curArice 4ate =and Time> dt dt&tart 4ouble d d&cale (nteger i i/ounter "#

*ong l l,igh/ounter &ingle =floating point> f f&ize &tring s s4epartmentCame 3ariant vnt vnt1nknown DbFect o o/ustomer /ollection col col/ustomers 1ser 4efined Type udt udtAoint Enum enm enm7ender

)rrays shall have no special prefi , but shall have a plural name, or a name ending )rray, for instance, sCames or l/ustomers)rray. S/o- Pr (i? s' &cope Arefi E ample &tatic sS sSb(s3alid !odule mS mSb(s3alid 7lobal gS gS(s3alid 3isual Basic control names will have a three character ,ungarian prefi as set out in the back of the 3isual Basic ArogrammerNs 7uide, for e ample t t is the prefi for a te tbo . (n addition, variables that point to a form will be prefi ed NfrmN, and general purpose variables for controls will be prefi ed NctlN. CONSTANT NAMING

;<

/onstants will have names that describe their use, and they shall be in upper case with underscores separating each word. There will be no requirement to specify a ,ungarian type prefi , but the same prefi es as variables shall be used to show module and global scope. PROCED%RE NAMING Arocedure shall have mi ed case descriptive names where the initial character of each word is in upper case. The names shall only e ceptionally contain abbreviations, and where abbreviations are used they shall be used consistently throughout the application. MOD%LE NAMING !odules, class, form and standard shall have descriptive names. They shall also have a one character prefi in upper caseM ? for forms, ! for standard modules, and / for class modules. This in particular helps distinguish the name of form modules from variables referencing a form instance. )bstract interfaces shall be prefi ed with a single upper case ( character. %s o( V+ri+:, s2 Pro/ .*r s +n. Const+nts @ V+ri+:, s 3ariables shall be e plicitly declared, and to this end Dption E plicit is to appear at the top of all modules. DbFect variables are not to be declared N)s Cew...N, rather they will be declared as the type of obFect and when an instance is required it will be created with the N&et ... T Cew ...N or by using /reateDbFect as appropriate. The generic form variable that is automatically created by 3B with the same name as the form modules is not to be used, rather, whenever an instance of a form is required a specific variable declared as the form type will be used. 3ariables shall be declared at the narrowest scope possible. 7lobal scope modules are to be avoided. ;"

*ocal variables shall be declared at the top of a procedure, not within the body. The 3ariant type shall only be used when no other more specific type is possible. 3ariables shall have a focused use. They shall not be declared once and used for several different purposes. &tring variables shall be concatenated with the ampersand character =i.e. U not O> Bhen naming boolean variables, the positive rather than the negative form shall be preferred, i.e. b(s3alid rather than b(sCot3alid. PROCED%RES Arocedures shall have an appropriate clearly defined scope =Aublic, Arivate or ?riend> and not rely on the default setting. Arocedures shall have as few e it points as possibleM E it ?unction@&ub and Aroperty are to be avoided unless it improves the readability. Arocedures shall have robust e it code where obFect references are e plicitly tidied up rather than relying on 3isual Basic to clean up as they go out of scope. P+r+) t rs s"+,, "+0 + s- /i(i . .+t+ t5- $ 4ata will be passed to and from procedures with parameters rather than module or global scope variables. Aarameters with a small range of values shall be declared with an enumeration type. Bhere parameters are not to be changed they shall be declared By3al unless there is some performance reason to declare them By'ef. CONSTANTS &ystem constants and enumerations shall be used wherever possible, for e ample, vb!inimized./onstants shall not be declared in multiple places, rather they shall be declared at a higher scope ./onstants shall always be used in place of Nmagic numbersN, the e ception to this being the initialisation of variables to < or " =i.e. initialising a loop counter>. /onstants ;;

shall

be

used

when

referring

to

elements

in

control

array,

for

e ample,

t tCame=?('&TSC)!E>.Te t COMMENTING CODE /omments shall specify what the purpose of the code is, it shall not simply repeat the code.)ll deviations from coding standards or good programming practice shall have a comment specifying the reasons why./omments shall be indented to the same level as the code that follows them. End.of.line comments shall be avoided, the e ception being in the declaration section if a comment for a variable declaration is required. /omments shall be specified with a apostrophe not with the antiquated 'em statement. Every procedure and module shall have a boilerplate that descibes it purpose and parameters. &olid comment lines =for instance NVVVVVVVV> are not to be used e cept in module or procedure boilerplates.

FORMATTING CODE The indent tab setting in the 3isual Basic Dptions shall be left at the default setting of E spaces. (ndenting and white space shall be used to make the code more readable, like the paragraphs of a book. Co more that one statement shall appear on a single line. 1se the continuation character to split long lines to make them more readable. The continuation lines shall be indented. In. nt /o. +s (o,,oAs' Between an (f statement and its End (f, Else or Else(f. Between an Else and its End (f. Between an Else(f and its Else or End (f. Between a &elect statement and its End &elect statement. Between each /ase statement in a &elect. Between a 4o statement and its *oop. Between a Bith statement and its End Bith. Between a ?or statement and its Ce t. Between an Edit or )ddCew method and its 1pdate or /ancel1pdate. ;%

 Between the start and end of a transaction. Bithin the declaration section to show subordination, for instance between a Type and its End Type. 6$B CODING DESIGN Every procedure shall contain error handling to capture and re.raise or report errors. The most specific type of obFect variable shall be used in a ?or Each..Ce t loop. )lways include a /ase Else in &elect /ase structures. &plit an (f statement to use an End (f even where there is only one statement to e ecute. Cever compare a boolean for equality with True or ?alse. 1se parenthesis to improve readability even when they are strictly not required. 1se upper case letters for 7oTo labels. 1se 7oTo only where it improves readability. 4o not use 7o&ub. 4o not use default properties, rather specify them e plicitly, for e ample t tCame.Te t T sCame The reference counter used in a ?or..Ce t loop shall not be used after the loop has finished. The antiquated Bhile..Bend loop shall not be used. /ompile Dn 4emand is not to be used in the 3isual Basic options. 4oEvents shall be avoided unless required, specifically, where a control or form is to be refreshed the 'efresh method shall be used in preference to 4oEvents. 6$C DATA FLO< DIAGRAM The data flow diagram =4?4> is a graphical tool used for e pressing system requirements in a graphical form. The 4?4 also known as the Lbubble chartW has the purpose of clarifying system requirements and identifying maFor transformations that will become programs in system design. Thus 4?4 can be stated as the starting point of the design phase that functionally decomposes the requirements specifications down to the lowest level of detail. ;E

The 4?4 consists of series of bubbles Foined by lines. The bubbles represent data transformations and the lines represent data flows in the system R%LES %SED FOR CONSTR%CTING A DFD Arocess should be named and numbered for easy reference. Each name should be representative of the process. The direction of flow is from top to bottom and from left to right. That is data flow should be from source to destination. Bhen a process is e ploded into lower level details, they are numbered. The name of the data stores, sources and destinations are written in capital letters. Arocess and data flow names have the first letter of each word capitalized. The 4?4 is particularly designed to aid communication. (f it contains dozens of process and data stores it gets too unwieldy. The rule of the thumb is to e plode the 4?4 into a functional level. (t is best to take each function separately and e pand it to show the e plosion in a single process. (f a user wants to know what happens within a given process, then the detailed e plosion of that process may be shown. DATA FLO< DIAGRAM

;9

6$D DATA&ASE DESIGN D+t+ Constr+ints )ll business in the world runs on business data being gathered stored and analyzed. Business managers determine a set of rules that must be applied to the data being stored to ensure its integrity. T5- s o( D+t+ Constr+ints

;H

There are two types of data constraints that can be applied to data being inserted into a database table .Dne type of constraint is called an (@D constraint. The other type of constraint is called a business rule constraint. IEO Constr+ints The input @output data constraint is further divided into two distinctly different constraints. T" Pri)+r5 K 5 Constr+int ,ere the data constraint attached to a column ensures5 X X That the data entered in the table column is unique across the entire column. That none of the cells belonging to the table column are left empty.

T" For i!n K 5 Constr+int ?oreign constraint establishes a relationship between records across a master and a detail table. The relationship ensures. X X 'ecords cannot be inserted in a detail table if corresponding records in the master table 'ecords of the master table cannot be deleted if corresponding records in the detail &*sin ss R*, Constr+ints does not e ist. table e ist.

The 4atabase allows the application of business rules to table columns. Business managers determine business rules.

The 4atabase allows programmers to define constraints at5

;8

X X

/olumn *evel Table *evel

Co,*)n L 0 , Constr+ints (f data constraints are defined along with the column definition where creating or altering a table structure, they are column level constraints. T+:, L 0 , Constr+ints (f data constraints are defined after defining all the table columns when creating or altering a table structure, it is a table level constraint. N*,, V+,* Con/ -ts ) C1** value is different from a blank of zero. C1** values are treated specially by the database. ) C1** value can be inserted into the columns of any data type. Not N*,, Constr+int D (in . +t t" Co,*)n L 0 , Bhen a column is defined as not null, then that column becomes a mandatory column .(t implies that a value must be entered into the column if the record is to be accepted for storage in the table. T" Pri)+r5 K 5 Constr+int Pri)+r5 K 5 Con/ -ts ) primary key in a table used to uniquely identify each row in the table .) primary key column in a table has special attributes. X X (t defines the column as a mandatory column i.e. the column cannot be left blank. The The date held across the column !1&T BE 1C(01E. CDT C1** attribute is active.

#$ Table name 5 /ustomer Y Arimary +ey 5 /usScode ;$

Co,*)n n+) /usScode /usSname /usSaddr /usS/on TinSno /&TSno

D+t+t5Cumber Te t !emo Te t Te t Te t

D s/ri-tion /ustomer /ode /ustomer Came /ustomer address /ustomer contact number Ta (dentification Cumber /entral &ales Ta Cumber

3$ Table name 5 (nvoice Y Arimary +ey 5 invoiceSno Co,*)n n+) (nvoiceSno (nvoiceSdate /usSname CoSofSitems TotalSamt Ta Sper Ta Samt CetSamt D+t+t5Cumber Te t Te t Cumber /urrency /urrency /urrency /urrency D s/ri-tion (nvoice Cumber (nvoice date /ustomer Came Cumber of (tems Total amount Ta Aercentage Ta )mount Cet )mount

6$ Table name 5 AroductSdet Y Arimary +ey 5 (temScode Co,*)n n+) (temScode (temSname 1D! 'ateSitem &upSname D+t+t5Cumber Te t Te t /urrency Te t D s/ri-tion (tem /ode (tem Cam 1nit of !easure 'ate per (tem &upplier name

7$ Table name 5 &alesSdetails Y Arimary +ey 5 &alesSno Co,*)n n+) &alesSno &alesSdate /usSname (temsSordered TotalSamt D+t+t5Cumber Te t Te t Cumber /urrency D s/ri-tion &ales number &ales date /ustomer Came (tems Drdered Total amount

B$ Table name 5 &tockSdet Y Arimary +ey 5 itemScode ;#

Co,*)n n+) (temScode (temSname &tockShand 'eorderSlevel

D+t+t5Cumber Te t Cumber Cumber

D s/ri-tion (tem code (tem Came &tock in ,and 'e.order *evel

C$ Table name 5 &upplierSdet Y Arimary +ey 5 supScode Co,*)n n+) &upScode supSname &upSaddr &upScon &upStin &upScst D+t+t5Cumber Te t !emo Te t Te t Te t D s/ri-tion &upplier code &upplier Came &upplier )ddress &upplier /ontact &upplier T(C &upplier /&T

6$F INP%T SCREEN (nput design is one of the most important phase system design. (nput design is the process where. The input received in the system are planned and designed, so as to get only necessary information from the user, eliminating the information that is not required. The aim of the input design is to ensure the ma imum possible levels of accuracy and also ensures that the input is accessible that is understood by the user. 6$G O%TP%T SCREEN Dne of the most important factors of the system is the output it produces. Dutput refers to the results and information that is generated by the system. Basically, the output from a computer system is used to communicate the result of processing to the user.

%<

Dutput design is the process that involves designing necessary outputs which helps the user according to their requirements. Efficient output design should improve the system relationship with the user and help in decision.making. Dutput of the computer is the most important and direct source of information to the user. Dutput design should improve the system in relationship with the user help in decision. making. Dnce the output document can be carried out a maFor form of output is the hand copy from the printer or writing the data into the file in a specified format.

7$ SYSTEM TESTING AND IMPLEMENTATION

7$# SYSTEM TESTING Testing is a process used to help identify the correctness, completeness and quality of developed computer software. Bith that in mind, testing can never completely establish the correctness of computer software.

&ystem testing of software or hardware is testing conducted on a complete, integrated system to evaluate the systemNs compliance with its specified requirements. &ystem testing falls within the scope of black bo testing, and as such, should require no knowledge of the inner design of the code or logic.

%"

)s a rule, system testing takes, as its input, all of the PintegratedP software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system=s>. The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together =called assemblages> or between any of the assemblages and the hardware. &ystem testing is a more limiting type of testingM it seeks to detect defects both within the Pinter.assemblagesP and also within the system as a whole. %NIT TESTING Bhen the programs have been coded and compiled and brought to working conditions, they must be individually tested with the prepared test data. )ny undesirable happening must be noted and debugged =error corrections>.

INTEGRATION TESTING Int !r+tion t stin! is the phase of software testing in which individual software modules are combined and tested as a group. (t follows unit testing and precedes system testing. (ntegration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.

&LACK &OX TESTING &,+/1 :o? t stin! takes an e ternal perspective of the test obFect to derive test cases. These tests can be functional or non.functional, though usually functional. The test designer selects valid and invalid input and determines the correct output. There is no knowledge of the test obFectNs internal structure. This method of test design is applicable to all levels of software testing5 unit, integration, functional testing, system and acceptance. The higher the level, and hence the bigger and more comple the bo , the more one is forced to use black bo testing to

%;

simplify. Bhile this method can uncover unimplemented parts of the specification, one cannot be sure that all e istent paths are tested.

<HITE &OX TESTING <"it :o? uses an internal perspective of the system to design test cases based on internal structure. (t requires programming skills to identify all paths through the software. The tester chooses test case inputs to e ercise paths through the code and determines the appropriate outputs. The logical flow of a program is sometimes counter intuitive, meaning that unconscious assumptions about flow of control and data may lead to make design errors that are uncovered only once path testing commences. Bhile white bo testing is applicable at the unit, integration and system levels of the software testing process, it is typically applied to the unit. Bhile it normally tests paths within a unit, it can also test paths between units during integration, and between subsystems during a system level test.

VALIDATION TESTING 3alidation testing provides the final assurance that software meets all functional, behavioral and performance requirements. 3alidation testing can be defined in many ways, but a simple definition is that validations succeed when the software functions in a manner that is e pected by the user. The software once validated must be combined with other system element. &ystem testing verifies that all elements combine properly and that overall system function and performance is achieved. )fter the integration of the modules, the validation test was carried out over by the system. (t was found that all the modules work well together and meet the overall system function and performance. )ccording to this testing marketing is error free. 7$3 SYSTEM IMPLEMENTATION

%%

&ystem (mplementation is the stage of the proFect when the theoretical design is tuned into working system. (f the implementation system stage is not carefully controlled and planned, it can cause chaos. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the users a confidence that the system will work and be effective. The implementation stage in a proFect involves, /areful Alanning investigation of the current system, checking constraints and the implementation. Training the staffs in the newly developed system. ) software application in general is implemented after navigating the complete life cycle method of a proFect. 3arious life cycle processes such as requirement analysis, design phase, verification, testing and finally followed by the implementation phase results in a successful proFect management. The software application which is basically a Bindows based application has been successfully implemented after passing various life cycle processes mentioned above. )s the software is to be implemented in a high standard industrial sector, various factors such as application environment, user management, security, reliability and finally performance are taken as key factors throughout the design phase.

7$6 MAINTENANCE PROCED%RE To backup is to create a redundant copy, so that if anything should happen to the original file, you have recourse to the backup. The process can be as simple as copying files to diskettes, but this soon becomes a problem where files are too big for diskette, where there are too many files, or where too many diskettes are required.

%E

) better solution is to use an archiver =such as BinZip> or a backup utility to create a single compressed file from a collection of data files, and to split this over as many diskettes as required. This uses fewer diskettes and allows large files to be backed up even if the file is larger than a diskette can hold. ?or large data sets, you may need to use a bulk storage medium such as tape, Zip disk, /4' or similar. These are generally faster and more reliable than diskettes. The systems ( set up will usually have a facility to backup data and core system files to the hard drive, and another to copy the most recent of such backups to diskettes. 2ou should use this whenever you have done more work than you would want to redo from scratch. (f your work is saved outside the designated data subtree then it wonNt be backed up by this processM you will have to make your own arrangements to back it up =BinZip, copy, etc.> 7$7 IMPLEMENTATION METHOD A%THORITY ) software application in general is implemented after navigating the complete life cycle method of a proFect. 3arious life cycle processes such as requirement analysis, design phase, verification, testing and finally followed by the implementation phase results in a successful proFect management. The software application which is basically a web based application has been successfully implemented after passing various life cycle processes mentioned above. )s the software is to be implemented in a high standard industrial sector, various factors such as application environment, user management, security, reliability and finally performance are taken as key factors throughout the design phase. These factors are analyzed step by step and the positive as well as negative outcomes are noted down before the final implementation. &ecurity and authentication is maintained in both user level as well as the management level. The data is stored in )ccess ;<<< as '4B!&, which is highly reliable and simpler to use, the user level security is managed with the help of password options and sessions, which finally ensures that all the transactions are made securely.

%9

The applications validations are made, taken into account of the entry levels available in various modules. Aossible restrictions like number formatting, date formatting and confirmations for both save and update options ensures the correct data to be fed into the database. Thus all the aspects are charted out and the complete proFect study is practically implemented successfully for the end users. 7$B MAINTAIN PROCED%RE SYSTEM TO %SERS !uch can be done during system setup to improve the survivability, maintainability and recoverability of the file system and its data, as discussed on the data management page. Thereafter, there are three tasks required on a regular basis5 /heck that sufficient free space is availableM ideally 9<!O on /5 volume /heck the file system for errors, and manage these 4efragment the file system once it is known to be error.free The tools used here are Bindows E plorer =or its P!y /omputerP incarnation>, &can4isk, and 4efrag. (f free space is low, you can clear .T!A files from the Bindows base directory. 7$C SEC%RITY MEAS%RE TAKEN ThereNs more on safe computing and malware. !alware includes viruses, worms, troFans, and increasingly invasive commercial applications, and management has several parts5 o 'isk avoidance and evaluation . choice of applications and system setup o 'isk avoidance and evaluation . user education and safe computing practice o 'isk detection and destruction . choice and use of antivirus software o +eeping abreast of malware . antivirus updates and ongoing user education o &imply running an antivirus utility is not enough, even if it is kept up to date[

%H

?or best performance, you can use on.demand rather than on.access antivirus scanners . but this requires the user to know when to use this, and act accordingly. 1pdating an antivirus generally involves these steps5 7o to antivirus vendorNs web site via =say> (nternet E plorer Cavigate to the download section of the site 4ownload any updates that are relevant, noting where these are saved E tract files from downloaded archive to the antivirus program directory &ome Bindows.based antivirus utilities may automate this process to some e tent, by accessing the (nternet directly from within the program. 2ou should check for updates at least once a week, and make sure your antivirus data files do not become more than a month out of date.

B$DOC%MENTATION
B$# HO< TO INSTALL THE PACKAGE

%8

3isual Basic is programming language developed by !icrosoft that runs on an event. driven platform. )mong utilized programming languages, 3isual Basic is relatively easy to understand. 4ownloading and installing the actual development software is the first step when writing in this language. 3isual Basic version H.<Ns last year of production was "##$. ?or users who still using the older operating systems, such as Bindows !E, it is the best choice for programming in 3B. Cewer versions of the program will not support an older operating system. (f you want a copy of 3isual Basic H.<, the installation procedure is quick and easy. B$3 HO< TO OPERATE THE PACKAGE Dpen the Beb page for !icrosoft 3isual &tudio on your computer. &tart the download by clicking the P4ownloadP button. Aut the file somewhere where you can find it easily, such as your desktop. *ocate the setup file PvbrunH<sp9.e eP on your hard drive. 4ouble click the setup file to start the installation wizard. 'ead the license agreement and click the PacceptP bo to begin installation. ?ollow the instructions provided by the installation wizard to install the program. B$6 SOME FRE9%ENT ERRORS AND SOL%TIONS )re you unable to open the 3BE =3isual Basic Editor> in !& )ccess databaseI (s your !icrosoft )ccess database, which has 3B) =3isual Basic for )pplications> code, inaccessibleI This behavior may indicate corruption of )ccess database obFects or entire database, and lead to inaccessibility of the database =!4B or )//4B>. 2ou need to restore database from a backup in such cases. ,owever, if the backup is either not complete or not available, access database recovery becomes need of hour. Bhen you attempt to open 3BE in !4B or )//4B database =by pressing the )lt O ?"" key>, you may encounter either of the below error messages5 The 3isual Basic for )pplications proFect in this database is corrupt. The module name Nmodule nameN is misspelled or refers to a module that doesnNt e ist. (f the invalid module name

%$

is in a macro, an )ction ?ailed dialog bo will display the macro name and the macroNs arguments after you click D+. Dpen the !acro window, and type the correct module name. Bhen you try to e it the )ccess database, application might stop responding and you may come across nay of the below error message5 This program has performed an illegal operation and will be shut down. (f the problem persists, contact the program vendor. !&)//E&& caused an invalid page fault in !&)//E&&.E-E at <"%85%<<;d#<#. )n application error has occurred and an application log is being generated. !&)//E&&.e e E ception access violation=o <<<<<<9>,)ddressM < %<<;dH$" B$7 HO< TO TAKE &ACK%P 3BH add.in which backs.up your source code. /ombined with the powerful ,istory 3iewer, AroFect. Backup has all the features to enable you to manage the full life.cycle development efforts of even the largest proFects. &afely, routinely, and securely maintain a logical and easily used archive of your 3B proFects throughout the entire development process. &eamlessly integrated into the 3isual Basic (4E, backups are performed silently in the background, saving you time and allowing you to focus on the proFect at hand without worrying about timely storage of your code revisions. ,ave you ever wanted to go back and look at how your code behaved before you made that last changeI ,ave you wished that you could restore your proFect to a previous state after something went wrongI )ll of these features and more are at your fingertips with AroFect. Backup

B$B <HAT TO DO <HEN A FILE IS CORR%PTED ISS%E' Bhat do you do when your file is corrupt.

%#

RESOL%TION' (> Try using the L&ave as /ompacted /opyW5 Dpen the file within ?ile!aker Aro )dvanced or ?ile!aker 4eveloper /hoose ?ile menu \ &ave ) /opy )s \ /ompacted copy =smaller> Test the file ((> Try using L'ecoverW Bhile the file is still closed, open ?ile!aker Aro or ?ile!aker 4eveloper /hoose ?ile menu \ 'ecover and select the damaged file, and click Dpen Test the file (((> Try reestablishing the inde es For +/" in. ? . (i ,.' Bith the database open, choose ?ile menu \ 4efine \ 4atabase. (n the 4efine 4atabase dialog bo , click the ?ields tab. 4ouble click on the inde ed field. (n the Dptions for ?ield dialog bo , click the &torage tab. 'emove the inde by selecting inde ing none. /lick D+ to close the Dptions for ?ield dialog bo . 7o back to the 4efine 4atabase. 4ouble click on the same inde ed field. (n the Dptions for ?ield dialog bo , click the &torage tab. Alace the inde back on for that field by selecting inde ing all. /lick D+ to close the Dptions for ?ield dialog bo , click D+ to e it the 4efine 4atabase dialog. Test the file

IVH %s t" r /o0 r5 -ro/ ss VH %s + :+/1*- /o-5 o( t" (i, $

E<

EXPLANATION' Alease keep in mind that these techniques will not guarantee complete recovery. (> The L&ave as /ompacted /opyW is the easiest and most effective fi for many cases. This process will copy all of the data and rebuild the tree structure of the database. This may cause data that should have been deleted to reappear if data was not correctly deleted. ((> The L'ecoverW command will skip over bad blocks of information. 'ecover is the ne t best option for less complicated solutions. 'ecover will fi order. (((> 'eestablishing the inde es may correct some relational issues. (3> The concept behind recovery process found in )nswer "9$< is to get a known good schema =structure> of the database and place the most recent data into this structure. (n order to prevent the same corruption from being imported into the database, we e port Fust the data as te t such as a merge file and import that merge file into the good structure =a merge file is a /omma &eparated te t file =/&3> but with field headers making it easier to match field names>. &ome things to keep in mind when importing during this process are5 /ontainer fields cannot be e ported in this fashion and any embedded pictures will have to be re.embedded with the original pictures. /alculations and summaries cannot be imported into and does not need to be imported into because they are based on the data. 4epending on if there is an auto.enter calculation=s>, you may or may not want to run the auto.entering process when importing. )fter importing, you should always double check the data to make sure you are getting the correct result. (t is also recommended that you store a good clone of the database for safe E" many problems, however it can occasionally remove some damaged records@obFects if necessary to get the file back in working

keeping along with backups in the event that you would have to resort to the recovery process. This will save you the step of finding a good backup and cloning the file=s>. 3> (f you use a backup file, you will be missing the data from the last time you backed up until this point.

C$ CONCL%SION
The goal of the proFect ORDER PROCESSING SYSTEM has been successfully achieved. The testing and implementation has been done in a step.by.step E;

process. Each module has been developed and tested individually to obtain the necessary required output in the desired form. The proFect has been done as user.friendly software for easy handling of transactions. The software developed has been designed and run to satisfy the requirements and needs of the organization as well as the end users. The system reduces the corruption of files like while the file transfer is done. (t has also resulted in quick retrieval and reference of required information, which is vital to the degrees of the organization. The entire system is documented and can be easily understood by the end users. The form are very user friendly and also easy to handle even by the beginners with very little effort and guidance.

D$ &I&LIOGRAPHY
&OOKS REFERRED

E%

". &teven ,olzner, L3isual Basic H.< Black BookW, ;<<% Edition, 4reamtech Aublications ;. 6effrey ). ,offer , 6oey ?. 7eorge , 6oseph &. 3alacich L!odern &ystem )nalysis and 4esignW ,Third Edition , Aerson Education Aublicatons %. 'oger & Aressman, L&oftware EngineeringW, ;<<< Edition, 4reamtech Aublications

<E&SITES REFFERED ". www.developerfusion.com ;. www.akadia.com

F$ APPENDIX

EE

LOGIN FORM

MEN% FORM E9

C%STOMER FORM EH

E8

S%PPLIER DETAILS FORM

E$

PROD%CT DETAILS

Ar + D t+i,s For) E#

SALES DETAILS FORM 9<

9"

INVOICE DETAILS FORM

9;

STOCK DETAILS FORM

9%

C%STOMER REPORT

9E

S%PPLIER REPORT

PROD%CT DETAILS REPORT 99

Ar + D t+i,s R -ort 9H

98

SALES DETAILS REPORT

INVOICE DETAILS REPORT 9$

9#

STOCK DETAILS REPORT

G$ CODING
S+, s D t+i,s Arivate &ub /ommand"S/lick=> 4ata'eport9.&how H<

End &ub Arivate &ub ?ormS1nload=/ancel )s (nteger> &creen.!ouseAointer T vb4efault End &ub Arivate &ub datArimary'&SError=By3al ErrorCumber )s *ong, 4escription )s &tring, By3al &code )s *ong, By3al &ource )s &tring, By3al ,elp?ile )s &tring, By3al ,elp/onte t )s *ong, f/ancel4isplay )s Boolean> NThis is where you would put error handling code N(f you want to ignore errors, comment out the ne t line N(f you want to trap them, add code here to handle them !sgBo P4ata error event hit err5P U 4escription End &ub Arivate &ub datArimary'&S!ove/omplete=By3al ad'eason )s )4D4B.Event'easonEnum, By3al pError )s )4D4B.Error, ad&tatus )s )4D4B.Event&tatusEnum, By3al p'ecordset )s )4D4B.'ecordset> NThis will display the current record position for this recordset datArimary'&./aption T P'ecord5 P U /&tr=datArimary'&.'ecordset.)bsoluteAosition> End &ub Arivate &ub datArimary'&SBill/hange'ecord=By3al ad'eason )s )4D4B.Event'easonEnum, By3al c'ecords )s *ong, ad&tatus )s )4D4B.Event&tatusEnum, By3al p'ecordset )s )4D4B.'ecordset> NThis is where you put validation code NThis event gets called when the following actions occur 4im b/ancel )s Boolean &elect /ase ad'eason /ase ad'sn)ddCew H"

/ase ad'sn/lose /ase ad'sn4elete /ase ad'sn?irst/hange /ase ad'sn!ove /ase ad'sn'equery /ase ad'sn'esynch /ase ad'sn1ndo)ddCew /ase ad'sn1ndo4elete /ase ad'sn1ndo1pdate /ase ad'sn1pdate End &elect (f b/ancel Then ad&tatus T ad&tatus/ancel End &ub Arivate &ub cmd)ddS/lick=> Dn Error 7oTo )ddErr datArimary'&.'ecordset.)ddCew E it &ub )ddErr5 !sgBo Err.4escription End &ub Arivate &ub cmd4eleteS/lick=> Dn Error 7oTo 4eleteErr Bith datArimary'&.'ecordset .4elete .!oveCe t (f .ED? Then .!ove*ast End Bith H;

E it &ub 4eleteErr5 !sgBo Err.4escription End &ub Arivate &ub cmd'efreshS/lick=> NThis is only needed for multi user apps Dn Error 7oTo 'efreshErr datArimary'&.'efresh E it &ub 'efreshErr5 !sgBo Err.4escription End &ub Arivate &ub cmd1pdateS/lick=> Dn Error 7oTo 1pdateErr datArimary'&.'ecordset.1pdateBatch ad)ffect)ll E it &ub 1pdateErr5 !sgBo Err.4escription End &ub Arivate &ub cmd/loseS/lick=> 1nload !e End &ub

Arivate &ub /ommand"S/lick=> 4ata'eport%.&how End &ub H%

Arivate &ub ?ormS1nload=/ancel )s (nteger> &creen.!ouseAointer T vb4efault End &ub Arivate &ub datArimary'&SError=By3al ErrorCumber )s *ong, 4escription )s &tring, By3al &code )s *ong, By3al &ource )s &tring, By3al ,elp?ile )s &tring, By3al ,elp/onte t )s *ong, f/ancel4isplay )s Boolean> NThis is where you would put error handling code N(f you want to ignore errors, comment out the ne t line N(f you want to trap them, add code here to handle them !sgBo P4ata error event hit err5P U 4escription End &ub Arivate &ub datArimary'&S!ove/omplete=By3al ad'eason )s )4D4B.Event'easonEnum, By3al pError )s )4D4B.Error, ad&tatus )s )4D4B.Event&tatusEnum, By3al p'ecordset )s )4D4B.'ecordset> NThis will display the current record position for this recordset datArimary'&./aption T P'ecord5 P U /&tr=datArimary'&.'ecordset.)bsoluteAosition> End &ub Arivate &ub datArimary'&SBill/hange'ecord=By3al ad'eason )s )4D4B.Event'easonEnum, By3al c'ecords )s *ong, ad&tatus )s )4D4B.Event&tatusEnum, By3al p'ecordset )s )4D4B.'ecordset> NThis is where you put validation code NThis event gets called when the following actions occur Pro.*/t D t+i,s 4im b/ancel )s Boolean &elect /ase ad'eason /ase ad'sn)ddCew HE

/ase ad'sn/lose /ase ad'sn4elete /ase ad'sn?irst/hange /ase ad'sn!ove /ase ad'sn'equery /ase ad'sn'esynch /ase ad'sn1ndo)ddCew /ase ad'sn1ndo4elete /ase ad'sn1ndo1pdate /ase ad'sn1pdate End &elect (f b/ancel Then ad&tatus T ad&tatus/ancel End &ub Arivate &ub cmd)ddS/lick=> Dn Error 7oTo )ddErr datArimary'&.'ecordset.)ddCew E it &ub )ddErr5 !sgBo Err.4escription End &ub Arivate &ub cmd4eleteS/lick=> Dn Error 7oTo 4eleteErr Bith datArimary'&.'ecordset .4elete .!oveCe t (f .ED? Then .!ove*ast End Bith H9

E it &ub 4eleteErr5 !sgBo Err.4escription End &ub Arivate &ub cmd'efreshS/lick=> NThis is only needed for multi user apps Dn Error 7oTo 'efreshErr datArimary'&.'efresh E it &ub 'efreshErr5 !sgBo Err.4escription End &ub Arivate &ub cmd1pdateS/lick=> Dn Error 7oTo 1pdateErr datArimary'&.'ecordset.1pdateBatch ad)ffect)ll E it &ub 1pdateErr5 !sgBo Err.4escription End &ub Arivate &ub cmd/loseS/lick=> 1nload !e End &ub

HH