10 Dhinesh Documentation 2007

8/10/2019 10 Dhinesh Documentation 2007

1/42

1

1. INTRODUCTION

The main purpose of this project is to computerize the human process held in the

organization. The process sequence was studied and required inputs were gathered, processed

and output and reports were produced.

The number of customers arrival is on a alarming rate on the manual calculations always

results in a errors which are great loss to the store.The new system will replace the existing

manual processing to overcome the drawbacks.

Visual Basic programming language is not unique to visual basic. The Visual Basic

programming systems, applications, edition included in Microsoft Excel, Microsoft Access and

many other applications use the same language.

1.1 SYSTEM SPECIFICATION

1.1.1 HARDWARE CONFIGURATION

PROCESSOR : PENTIUM

RAM : 128 MB

FDD : 1.44 MB 3.5 INCHHDD : 20 GB

MONTIOR : SVGA COLOR MONITOR

KEYBOARD : 104 KEYS SAMSUNG KBD

MOUSE : LOGITECH MOUSE

1.1.2 SOFTWARE SPECIFICATION

FRONT END : VISUAL BASIC 6.0

BACK END : MS ACCESS

PLATFORM : WINDOWS 98


2/42

2

SOFTWARE DESCRIPTION

VISUAL BASIC 6.0

Visual Basic is an ideal programming language for developing sophisticated professional

applications for Microsoft windows. Microsoft Visual Basic is the fastest and easiest tool to

create application for Microsoft Windows.

The VISUAL part refers to the method used to create the Graphical User screen

Interface (GUI). Rather than writing numerous lines of codes to describe the appearance &

location of interface elements, pre built objects can be simply added in the light place on.

The Basic part refers to the BASIC language used by most programmers language than

any other language. Visual Basic has evolved from the original BASIC & now contains several

hundred statements, functions & keywords, many of which relate directly to the windows GUI.

Visual Basic 6.0 for Windows required at least Microsoft Windows NT 3.51 or later with

a very fast 486 or Pentium processors computer & at least 10MB of RAM. A complete

installation of the moist powerful version of Visual Basic 6.0, the enterprise edition requires

more than 140MB of hard disk space.

Visual Basic programming language is not unique to visual basic. The Visual Basic

programming systems, applications, edition included in Microsoft Excel, Microsoft Access and

many other applications use the same language. The Visual Basic scripting edition is widely used

scripting language & a subset of the visual basic language.


3/42

3

MS-ACCESS

Access can be used to develop both simple and complex database. Its wonderfully

designed built-in wizard makes allow look like a product that anyone can use. Although it is true

that the simplest of the access application can be produced without any thought of design and

without a single line of code written by the user, most applications require at least some

designing and customer codes.

It can be develop five general types of applications.

1. Personal applications

2. Applications used to run small business

3. Departmental applications

4. Corporation wide applications

5. Client / Server applications.


4/42

4

2. SYSTEM STUDY

2.1 EXISTING SYSTEM

The existing system is manual one .The major activities are related to clients or

customers are usually carried out in a hectic way. The number of customers arrival is on a

alarming rate on the manual calculations always results in a errors which are great loss to the

store. Even though mostly nowadays the computers find there place everywhere.

Here, there has been confusion on the installation of system and what kind of software

they were going to use. And of lately this package which was proposed that they have thought of

implementing a change so the existing system has been manual one and it has been burden on

various activities where all needed to carry out the existing system.

2.1.1 DRAWBACKS OF EXISTING SYSTEM

1.

Erroneous data entry due to human errors.

2. Searching and verifying of exact data are more time consuming.

3. Reports are not in a presentable form.

4. Loss of past records due to mishandling and improper storage facilities.

5. Slow processing.


5/42

5

2.2 PROPOSED SYSTEM

In order to conduct a success project we must understand the scope of work to be done,the risk to be incurred the resources, the required task to be accomplished the mile stones to be

tracked the fort it be expended and the schedules to be followed. It begins before technical work

starts, continues as a software evolutes from the concept of reality and only on the software is

retired.

The system use less amount of time to produce report. In the computerization of the

concern, the errors can be rectified. The proposed system is used mainly to maintain the

organization. The new system will replace the existing manual processing to overcome the

drawbacks. It maintains all the customer details, order details and the checking process through

the system.

2.2.1 FEATURES OF PROPOSED SYSTEM

It is very accurate

It can store larger amount of data i.e., memory is very large and can have a backup copy when needed.

Very good at repeated calculations.

All the process has done at high speed.

It does the work very efficiently.

It is cost effective.

Reduced paper work.


6/42

6

3. SYSTEMDESIGN AND DEVELOPMENT

3.1 INPUT DESIGN

The main objective in input design is to specify how the information is put into a

term that is acceptable to computer. The files and database information, frequency and

certification requirements are considered in the selection of input format. Another objective is to

ensure that input is acceptable and understandable to user.

Input design is the process of converting user-originated inputs to a computer- based

format. The goal of input is to make data-entry as easy and it shall be free from error as possible.

A well-designed input should serve five purposes

1.control workflow.

2.To reduce redundancies in recording data.

3.controlling errors.

4.To allow easier checking of data.

5.controlling the amount of input required.

When the data is fed into a system, the operator must receive the data in a form that

can be understood readily. The operator should key the data in the order in which it occurs on the

form and the computer should reformat it as required.

The following input design forms are presented in the project:

1.Customer

2.Purchase

3.Checking

4.Dyeing

5.Garments

6.Customer Order

7.Sales


7/42

7

1.CUSTOMER FORM:

This form contains five fields such as CUSTCODE,ADDRESS,CUSTNAME,PHONE

EMAILID.This screen is attached on page no:31.

-CUSTCODE is used to store the customer code.

-CUSTNAME is used to store the customer name.

-ADDRESS is used to store the customer address.

-PHONE used to store the customer phone number.

-EMAILID used to store the customer email id.

2.PURCHASE FORM:

This form contains eight fields such as PURDT,COUNTS,VARIETY,QTY,

PRICE,TOTAL,COMP,ADDRESS. This screen is attached on page no:32.

-PURDT is used to store the purchase date.

-COUNTS is used to store the purchase counts.

-VARIETY is used to store the purchase varity.

-QTY is used to store the purchase quality.

-PRICE is used to store the purchase price.

-TOTAL is used to store the purchase total.

-COMP is used to store the purchase company.

-ADDRESS is used to store the address.


8/42

8

3.CHECKING FORM:

This form contains eight fields such as CHKDT,COUNTS,VARIETY,LOOMNO,

ROLLQTY,DAMAGEQTY,WARHOUSEQTY,DESIGN. This screen is attached on page

no:33.

-CHKDT is used to store the checking date.

-COUNTS is used to store the counts.

-VARIETY is used to store the variety.

- LOOMNO is used to store the loom number.

-ROLLQTY is used to store the roll quality.

- DAMAGEQTY is used to store the damage quality.

- WARHOUSEQTY is used to store the warhouse quality.

- DESIGN is used to store the design.

4.DYEING FORM:

This form contains eight fields such asDYINGDT,COUNTS,VARIETY,

BUNDLENO,QTY,DESIGNING,OUTPUTQTY,OUTPUTBUNDLENO. This screen isattached on page no:34.

- DYINGDT is used to store the dyeing date.

- COUNTS is used to store the dyeing counts.

-VARIETY is used to store the dyeing variety.

- BUNDLENO is used to store the bundle number.

-QTYis used to store the dyeingquality.

- DESIGNING is used to store the dyeing designing.

-OUTPUTQTY is used to store the dyeing output quality.

- OUTPUTBUNDLENO is used to store the dyeing output bundle number.


9/42

9

5.GARMENTS FORM:

This form contains ten fields such as GARDT,COUNTS,VARIETY,DESIGNING,

ITEMTYPE,REQMINQTY,NOOFPIECES,REQTOTQTY,PRICE,TOTAMT. This screen is

attached on page no:35.

-GARDT is used to store the garment date.

- COUNTS is used to store the garment counts.

- VARIETY is used to store the garment variety.

- DESIGNING is used to store the garment designing.

- ITEMTYPE is used to store the garment item type.

- REQMINQTY is used to store the garment require minimum quality.

-NOOFPIECES is used to store the garment number of pieces.

-REQTOTQTYis used to store the garment required total quality.

-PRICE is used to store the garment price.

-TOTAMT is used to store the garment total amount.

6.CUSTOMER ORDER FORM:

This form contains eleven fields such as ORDDT,DESIGNING,NOOFPIECES,PRICE,TOTAMT,DELDT,CUSTCODE,CUSTNAME,ADDRESS,PHONE,ORDNO. This

screen is attached on page no:36.

-ORDDT is used to store the order date.

-DESIGNING is used to store the designing.

-NOOFPIECES is used to store the number of pieces.

-PRICE is used to store the price.

-TOTAMT is used to store the total amount.

-DELDT is used to store the delivery date.



-ADDRESS is used to store the address.


10/42

10

-PHONE is used to store the phone.

-ORDNO is used to store the order number

- REQTOTQTY is used to store the garment required total quality.

- PRICE is used to store the garment price.

- TOTAMT is used to store the garment total amount.

7.SALES FORM:

This form contains eleven fields such as INVNO,INVDT,CUSTCODE,CUSTNAME,

ADDRESS,DESIGNING,NOOFPIECES,PRICE,TOTAMT,ORDDT,ORDNO. This screen

is attached on page no:37.

-INVNO is used to store the invoice number.

-INVDT is used to store the invoice date.



-ADDRESS is used to store the address.-DESIGNINGis used to store the designing.

-NOOFPIECESis used to store the number of pieces.

-PRICEis used to store the price.

-TOTAMTis used to store the total amount.

-ORDDTis used to store the order date.

-ORDNOis used to store the order number.


11/42

11

3.2 OUTPUT DESIGN

The primary considerations in output design is to arrange the data in a form most

convenient to the user in dealing with output, the basic elements of a form, are Pre-printed

information and data to be filled in by the user must again be considered.

Computer programmers are expected to have fairly good concept of how to display

computers output for users to readily understand it. Since the computer can store and print

deceptive information as well as data, an important task of both the system analyst and the

programmer is to determine which pre-printed are respective information should be provided on

each page or printed output or each visual display of output

The following output design reports are presented in the project:

1.Purchase

2.Checking

3.Dyeing

4.Garments

5.Customer Order

1.PURCHASE REPORT

This report is viewed in date wise.This output display the purchase details like purchase

date,company,address.counts.price,varity.quality,total. This report is attached on page no:38.

2.CHECKING REPORT

This report is viewed in date wise.This output display the checking date,varity,counts,loom number,roll quality,damage quality,warhouse quality,design.This report is attached on page

no:39


12/42

12

3.DYEING REPORT

This report is viewed in date wise.This output display the dyeing date,counts ,varity,

bundle number,quality,design,output quality,output bundle number.This report is attached on

page no:40.

4.GARMENTS REPORT

This report is viewed in date wise.This output display the garment date,count,varity,

designing,item type,number of pieces,required total quality,price,total amount.This report is

attached on page no:41.

5.CUSTOMER ORDER

This report is viewed in date wise.This output is display the order date,customer code,

number,order,customer name,address,phone number,designing,number of pieces,price,total

amount,delivery date.This report is attached on page no:42.


13/42

13

3.3 DATABASE DESIGN

A table may be defined as a collection of items of data recognized in to records in such a

way that specific items of data or records can be retrieved and accommodated in main storage

required for processing. Table design is an important activity in the design stage. Various factors

such as purpose of files, availability of the hardware , method of access, the activity and size of

the file etc, are considered during the table design.

This project use six database design that are ,

1.Customer

2.Purchase

3.Checking

4.Dyeing

5.Garments

6.Customer Order

1.CUSTOMER

This database is used to store the customer deatails.It use many fields like customer code

as text,name as text,address as text,phone number as number,e mail id as text/number.This table

is attached in the page no:24

2.PURCHASE

This database is used to store the customer deatails.It use many fields like purchase date

as date/time,company as text,address as text,count as number,price as number,varity as

text,quality as number,total as number. This table is attached in the page no:24


14/42

14

3.CHECKING

Ihis database is used to store the customer deatails.It use many fields like checking date

as date/time,count as text,varity as text,loom number as number,roll quality as number, damage

quality as number,warhouse as number,design as text. This table is attached in the page no:25

4.DYEING

This database is used to store the customer deatails.It use many fields like dyeing date as

date/time,counts as number,varity as text.bundle number as number,quality as number ,design as

text,output quality as number,output bundle as number. This table is attached in the page no:26

5.GARMENTS

This database is used to store the customer deatails.It use many fields like garment date

as date/time,counts as number,varity as text,designing as text,item type as text,number of pieces

as number,required total quality as number,price as number,total amount as number. This table is

attached in the page no:26

6.CUSTOMER ORDER

This database is used to store the customer deatails.It use many fields like order number

as number,order date as text/number,customer code as number,customer name as text,address as

text,phone number as number,designing as text,number of pieces as number,price as

number,total amount as number,delivery date as number/text. This table is attached in the page

no:25


15/42

15

3.4 SYSTEM DEVELOPEMENT

3.4.1 DESCRIPTION OF MODULES

MODULES:

1. Customer

2. Purchase

3.

Checking

4. Customer order

5. sales

1. CUSTOMER

This module is used to maintain the customer details. This page is used for storing,

Displaying and modifying the customers information. The page should display the Display

informations in a grid and it should also allow the user to find out a customer from the database

depending upon his name or id. It should provide the necessary controls for data entry.

2. PURCHASE

This module is used to maintain the purchase details.This page is used to enter the

purchases made from the garment companies and the suppliers. Proper tracking of all purchases

are very essential. Also take care to update the stock.This page is used for enter the purchase

information such as purdt, county, verity , qty, price, total amount etc.,


16/42

16

3.CHECKING

This module is used to maintain the checking details. This is also a master entry form to

enter the details of the daily expense. All the details of the daily expense of the user can be

entered in this form.

4. CUSTOMER ORDER

This module is used to maintain the customer order details. It can used for easily view

and update the customer orders. It have the fields like orddt, designing noofpieces, price, totamt,

etc.

5.SALES

This module is used to maintain the sales details. Sales entry form is used to enter the

sales made to the distributors and customers. Proper tracking of all sales is very essential. Also

take care to update the stock. This page is used to enter the sales information such as invno,

invdt, noofpieces, price, totamt, etc.


17/42

17

4.TESTING AND IMPLEMENTATION

SYSTEM TESTING

When the staffs have been trained, a full system test can be aimed to ensure that the

system works accurately and efficiently before live operation commences. System providing is

and ongoing activity thoroughly and continually examined on paper to ensure that they will work

when implemented.

When the programmers have tested each programs individually using test data designed

by themselves and have verified that these programs unit specification. The complete system

and its environment must be tested to the satisfaction of the system analysts and the user. The

results of the processed test data should be maintained as a permanent manual subsequent major

amendment. This stage in the development of system is to test the developed system with data

(Trial Run) and then make necessary changes. Testing is done in three steps.

Testing the functional performance of each individual modular component.

Testing the function and interface of the software.

Testing to find out weather all requirements have been met.

The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a way to check the

functionality of components, sub assemblies, assemblies and/or a finished product It is the

process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an

unacceptable manner. There are various types of test. Each test type addresses a specific testing

requirement.


18/42

18

TYPES OF TESTING

unit testing

integration testing

functional test

system test

white box testing

black box testing

UNIT TESTING

Unit testing involves the design of test cases that validate that the internal program logic is

functioning properly, and that program inputs produce valid outputs. All decision branches and

internal code flow should be validated. It is the testing of individual software units of the

application .it is done after the completion of an individual unit before integration. This is a

structural testing, that relies on knowledge of its construction and is invasive. Unit tests perform

basic tests at component level and test a specific business process, application, and/or system

configuration. Unit tests ensure that each unique path of a business process performs accurately

to the documented specifications and contains clearly defined inputs and expected result.

INTEGRATION TESTING

Integration tests are designed to test integrated software components to determine if they

actually run as one program. Testing is event driven and is more concerned with the basic

outcome of screens or fields. Integration tests demonstrate that although the components wereindividually satisfaction, as shown by successfully unit testing, the combination of components is

correct and consistent. Integration testing is specifically aimed at exposing the problems that

arise from the combination of components.


19/42

19

FUNCTIONAL TEST

Functional tests provide systematic demonstrations that functions tested are available as

specified by the business and technical requirements, system documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures : interfacing systems or procedures must be invoked.

SYSTEM TEST

System testing ensures that the entire integrated software system meets requirements. It tests a

configuration to ensure known and predictable results. An example of system testing is the

configuration oriented system integration test. System testing is based on process descriptions

and flows, emphasizing pre-driven process links and integration points.

WHITE BOX TESTING

White Box Testing is a testing in which in which the software tester has knowledge of the

inner workings, structure and language of the software, or at least its purpose. It is purpose. It is

used to test areas that cannot be reached from a black box level.

BLACK BOX TESTING

Black Box Testing is testing the software without any knowledge of the inner workings,

structure or language of the module being tested. Black box tests, as most other kinds of tests,

must be written from a definitive source document, such as specification or requirements

document, such as specification or requirements document. It is a testing in which the software

under test is treated, as a black box .Tester cannot see into it. The test provides inputs and

responds to outputs without considering how the software works.


20/42

20

SYSTEM IMPLEMENTATION

System Implementation is an important stage of the project where the theoretical design

is turned into the practical system. The main stages of implementation are as follows:

1. Implementation Planning

2. Training User Staff

Implementation Planning is the first task in system implementation, planning means

deciding on the methods and time scale to be adopted. Once the planning is over the major effort

in the Computer department is to ensure that the programs in the system are working properly.

During the Training the user department should concentrate on training user staff. When

the staffs in the user department have been trained a full system test can be carried out, involving

both computer and clerical problems.


21/42

21

5.CONCLUSION

This system has been developed for the conditions existing at present and other

difficulties at runtime. This system is easy and flexible. Also it is implemented successfully.

This project may applicable for other General Purpose Stores to maintain the stocks and

for billing. Any suggestions regarding the improvement of this project are easily extended in

future.

The number of customers arrival is on a alarming rate on the manual calculations always

results in a errors which are great loss to the store.The system use less amount of time to produce

report. In the computerization of the concern, the errors can be rectified.

The proposed system is used mainly to maintain the organization. The new system will

replace the existing manual processing to overcome the drawbacks.


22/42

22

6.BIBLIOGRAPHY

1. Elias M.Awad, System Analysis and Design Galgotia Publications Pvt. ltd, 1997,

Second Edition.

2. Richard Fairly, Software Engineering, McGraw-Hill, International Edition.

3. Rob Thayer , Unleased Visual Basic 6.0.

4. John Paul Meller, The Complete Reference Visual Basic 6.0.

5. Visual Basic Reference Book MaterialIntegrity Solutions

6. Visual Basic 5.0 Training guideMurray.

7. Visual Basic Black book-Steven Holzner.

8. Mastering Visual Basic 6.0-Evangelos Petroutsos.

9. Visual Basic 6-Rajendra saiokhie.

WEBSITES :

www.dotnetmasters.com

www.gfxtra.com

www.a1vbcode.com

www.google.co.in
http://www.dotnetmasters.com/http://www.gfxtra.com/http://www.a1vbcode.com/http://www.google.co.in/http://www.google.co.in/http://www.a1vbcode.com/http://www.gfxtra.com/http://www.dotnetmasters.com/


23/42


24/42

24

B) TABLE STRUCTURE

CUSTOMER TABLE

S.No Field Name Type Description

1 Customer code Number CUSTOMER CODE

2 Customer Name Text CUSTOMER NAME

3 Address Text ADDRESS

4 Ph Number PHONE NUMBER

5 Mail id Text EMAIL ID

PURCHASE DETAILS


1 Purchase Date Date/Time PURCHASE DATE

2 Purchase Item Text PURCHASE ITEM

3 Address Text ADDRESS

4 Count Number COUNT

5 Price Number PRICE

6 Quantity Number QUANTITY

7 Total Number TOTAL


25/42

25

CHECKING DETAILS


1 ChkDt Date/Time CHECK DATE

2 Counts Text COUNTS

3 Variety Text VARIETY

4 LoomNo Number LOOM NUMBER

5 RollQty Number ROLL QUALITY

6 DamageQty Number DAMAGE QUALITY

7 WarhouseQty Number WARHOUSE QUALITY

8 Design Text DESIGN

CUSTEMER ORDER DETAILS


1 OrdDt Date/Time ORDER DATE

2 Designing Text DESIGNING

3 NoOfPieces Number NUMBER OF PIECES

4 price Number PRICE

5 TotAmt Number TOTAL AMOUNT

6 DelDt Date/Time DELIVERY DATE

7 CustCode Text CUSTOMER CODE

8 CustName Text CUSTOMER NAME

9 Address Text ADDRESS10 Phone Text PHONE NUMBER

11 OrdNo Text ORDER NUMBER


26/42

26

DYEING DETAILS

GARMENTS DETAILS


1 GarDt Date/Time GARMENT DATE




5 ItemType Text ITEM TYPE

6 ReqMinQty Number REQUIRED MINIMUM QUALITY

7 NoOfPieces Number NUMBER OF PIECES

8 ReqTotQty Number REQUIRED TOTAL QUALITY

9 Price Number PRICE

10 TotAmt Number TOTAL AMOUNT


1 DYINGDT Date/Time DYEING DATE



4 BundleNo Number BUNDLE NUMBER

5 Qty Number QUALITY


7 OutputQty Number OUTPUT QUALITY

8 OutputBundleNo Number OUTPUT BUNDLE NUMBER


27/42

27

C) SAMPLE CODING

Dim WithEvents adoPrimaryRS As Recordset

Dim mbChangedByCode As BooleanDim mvBookMark As Variant

Dim mbEditFlag As Boolean

Dim mbAddNewFlag As Boolean

Dim mbDataChanged As Boolean

Private Sub Combo1_Click()

txtFields(1).Text = Combo1.TextEnd Sub

Private Sub Combo2_Click()

txtFields(2).Text = Combo2.TextEnd Sub

Private Sub Combo3_Click()txtFields(7).Text = Combo3.Text

End Sub

Private Sub Form_Load()Dim db As Connection

Set db = New Connection

db.CursorLocation = adUseClientdb.Open "PROVIDER=Microsoft.Jet.OLEDB.3.51;Data Source=" & App.Path &

"\Garments.mdb;"

Set adoPrimaryRS = New Recordset

adoPrimaryRS.Open "select

ChkDt,Counts,Variety,LoomNo,RollQty,DamageQty,WarhouseQty,Design from Checking

Order by ChkDt", db, adOpenStatic, adLockOptimisticDim oText As TextBox

'Bind the text boxes to the data provider

For Each oText In Me.txtFields

Set oText.DataSource = adoPrimaryRSNext


28/42

28

Module1.ConConnection

Module1.ComboItems "Purchase", "Counts", "Combo1", MeModule1.ComboItems "Purchase", "Variety", "Combo2", Me

Combo3.AddItem "Plain Satin"

Combo3.AddItem "Flower Checked"Combo3.AddItem "Twil Satin"Combo3.AddItem "Strips"

Combo3.AddItem "Checked with Colors"

Combo3.AddItem "Torkey Towell"

mbDataChanged = False

End Sub

Private Sub Form_Resize()

On Error Resume Next

lblStatus.Width = Me.Width - 1500cmdNext.Left = lblStatus.Width + 700

cmdLast.Left = cmdNext.Left + 340

End Sub

Private Sub Form_KeyDown(KeyCode As Integer, Shift As Integer)

If mbEditFlag Or mbAddNewFlag Then Exit Sub

Select Case KeyCode

Case vbKeyEscape

cmdClose_Click

Case vbKeyEndcmdLast_Click

Case vbKeyHome

cmdFirst_ClickCase vbKeyUp, vbKeyPageUp

If Shift = vbCtrlMask Then

cmdFirst_ClickElse

cmdPrevious_Click

End If

Case vbKeyDown, vbKeyPageDownIf Shift = vbCtrlMask Then

cmdLast_Click

Else

cmdNext_ClickEnd If

End Select

End Sub


29/42

29

Private Sub Form_Unload(Cancel As Integer)

Screen.MousePointer = vbDefaultEnd Sub

Private Sub adoPrimaryRS_MoveComplete(ByVal adReason As ADODB.EventReasonEnum,ByVal pError As ADODB.Error, adStatus As ADODB.EventStatusEnum, ByVal pRecordset AsADODB.Recordset)

'This will display the current record position for this recordset

lblStatus.Caption = "Record: " & CStr(adoPrimaryRS.AbsolutePosition)End Sub

Private Sub adoPrimaryRS_WillChangeRecord(ByVal adReason As

ADODB.EventReasonEnum, ByVal cRecords As Long, adStatus As ADODB.EventStatusEnum,ByVal pRecordset As ADODB.Recordset)

'This is where you put validation code

'This event gets called when the following actions occurDim bCancel As Boolean

Select Case adReason

Case adRsnAddNewCase adRsnClose

Case adRsnDelete

Case adRsnFirstChangeCase adRsnMove

Case adRsnRequery

Case adRsnResynch

Case adRsnUndoAddNewCase adRsnUndoDelete

Case adRsnUndoUpdate

Case adRsnUpdateEnd Select

If bCancel Then adStatus = adStatusCancelEnd Sub

Private Sub cmdAdd_Click()

On Error GoTo AddErrWith adoPrimaryRS

If Not (.BOF And .EOF) Then

mvBookMark = .Bookmark

End If


30/42

30

.AddNew

lblStatus.Caption = "Add record"

mbAddNewFlag = True

SetButtons FalseEnd WithtxtFields(0).Text = Format(Date, "dd/mmm/yyyy")

Exit SubAddErr:

MsgBox Err.Description

End Sub

Private Sub cmdDelete_Click()

On Error GoTo DeleteErr

With adoPrimaryRS.Delete

.MoveNext

If .EOF Then .MoveLast

End WithExit Sub

DeleteErr:

MsgBox Err.DescriptionEnd Sub

Private Sub cmdEdit_Click()

On Error GoTo EditErr

lblStatus.Caption = "Edit record"

mbEditFlag = TrueSetButtons False

Exit Sub

Documents

10 Dhinesh Documentation 2007