Database SSK3408-Chapter04

8/10/2019 Database SSK3408-Chapter04

1/37

1

Database Application DevelopmentDatabase Application DevelopmentSSK 3408SSK 3408

Chapter 4Chapter 4Forms and ReportsForms and Reports


2/37

Learning ObjectivesExplain the purpose of forms and reports.

Explain the types of forms and reports.Explain the basic human factors involved when

2

.Explain the controls to be used on forms.Describe the basic and complex components of

forms.Describe the overall structure of reports.


3/37

3

Provides a better interface to users when working

with databasesMakes it easy for non technical users to extractdata from the database

Forms

Provides a customizable view that summarizesdata and limits user access as needed


4/37


5/37

5

Important to understand that forms are the primary

contact to the usersTo the user, the Form is the system

The form must be tailored for specific tasks needs

Effective Design of Forms

Designer must determine the needs of the user as usermay not be aware of the capabilities and limitation ofa modern DBMS.

Research into human factors design providesguidelines in creating an effective form.


6/37

6

Basics human factors elements involves:-

1. User controlThe users should always has control over the system.For example:

Let the users decide the sequence in entering data.

Human Factors Design

User customization such as flexibility in sorting results and data to beincluded in reports.

2. ConsistencyForm layout and button actions are uniform throughout the system.

3. ClarityForms must be well organized, simple and the purpose of the formmust be unambiguous.For example, if a company refers to its employee as Associatesthen use that term instead of Employee.


7/37

7

4. Aesthetics

Effective use of color and design to provide an attractivework environment to users.

5. Feedback

Human Factors Design ..cont.

auditory responses.

6. ForgivenessRequire user confirmation on major changes and allowusers to undo or correct mistakes.For example, deletion confirmation to provide chances tothe user to undo the deletion.


8/37

8

Designing applications that run under Windows

requires a solid understanding of the WindowsInterface.To provide standard controls and operations as offered

Interface Standards

by Windows.Windows functionality enables us to provide additionaland powerful features within our application.

Standardization guarantees that frequently usedcommands provide the same action regardless ofsoftware.


9/37

Navigation and ChoicesMouse, IconsKeyboard, Short-cutsMenus

Manipulation

ActivationDrag and DropFeedback

9 Windows Interface Standards

e ec ons rom a sSingleContiguous MultipleDisjoint Multiple

FocusOutline box

Cursor

Progress indicators andstatus gaugesFlashingTool tipsStatus barMessage boxes


10/37

Basic window components:Frame (sizing)Title barControl-menu boxButtons

10 Window Controls

MaximizeMinimizeCloseScroll bar

A window consists of several common components.

Other features or commands can be added as required by the tasks.


11/37

Menus to provide access toprimary functions for each taskType of menu:

Drop-down

11 Windows Menu

Mnemonic characterPop-up (as needed)

Biggest different between a pop-up and standard, fixed menu isthat a pop-up menu is usuallycontext sensitive (customizedfunctions depending on theselected object)


12/37

Message BoxesTitleMessageSimple buttonsIcons

12 Message Box

A message box is generally used to interrupt a taskand provides important messages.

A message box can also be a modal form whichforces a user to provide a response


13/37

13

Biggest drawback to the Windows design standard

is accessibilityGraphical approach is inappropriate for physicallychallenged users

User Interface Accessibility

Certain users require special add-on software tonavigate a computer screen

E.g. Screen narration/reader software for the blind


14/37

1. Provide multiple inputmethods

KeyboardMouse

Some Suggestions:Beware of high contrastcolors (Red/Green).Avoid requiring rapid user

14 Accessibility Guidelines

o ce

2. Provide multiple outputmethods

VisualSoundColor

Avoid rapid flashing on thescreen.Give users customizationoptions.

VolumeColorTypefaces & Fonts


15/37

There are many different ways to design forms

and suit them to user tasks.Each form contains controls that can be used toperform actions or interact with the forms

15 Form Layout

Types of FormsTabular

Single Row

Sub-forms (one-to-many)

Switchboard

Controls

Form

Order

11 Dog 57 Dog 1

13 Cat 2

Items


16/37

Works best to display the entire contents of 1 table

Designer can control data entry sequence.Probably include buttons for sorting.

16 Tabular Form


17/37

Data for only one row.

Similar in appearance topaper forms.Can use color, graphics, and

17 Single Row (Columnar) Form

uthe form easier to use.Records can be browsedusing navigation buttonsCan be used with sub formsto show related data fromother tables


18/37

Typically a one-to-many relationship.Sub-form contents are linked to the main form through acommon column (not displayed on the sub-form.)Can have multiple sub-forms (Independent or Nested).

18 Sub-Form


19/37

19

Sale

An alternative to using sub-forms A command control is used to display a child form based on

key data of the parent form Prevents accidental modification deletion of data

Multiple Forms

CustomerFirstName: MaryLastName: JonesAddress: 123 Oaxaca Ave.

Animals Purchased

Merchandise

EditFirstName: Mary

LastName: Jones

Address: 123 Oaxaca Ave.

City: Los Angeles

ZipCode: 90086

Gender: Female

Age: 20

AccountBalance: $150


20/37

A blank form used

as a menuNormally used tochoose task from a

20

Switchboard Form

list of availableactions.Can also be used to

identify user orgroups


21/37

Queries are used to automatically look up data.e.g., Customer name, Product description

Queries are used in retrieving and updating

21

Queries

.Be very careful when using queries.

Each form should store data in only one table.

For multiple tables, use a sub-form or separateforms.Usually lock the look up data (parent form) so itcannot be changed accidentally.


22/37

Clerk enters a CustomerID.

Stored in the Order table.Query joins Sale and Customer.

22

Query Form Example

.Matching name is displayed on the form.Does not display the join column (CustomerID) fromthe look up table (Customer).

Customer Order1234SaleID

17CustomerID7/25/01Date

Carly Embry


23/37

23

Customer Order1234SaleID

17CustomerID7/25/01Date

Carly Embry

Form Query: Underlying Tables

SaleID CustomerID Sdate1232 23 7/24/011233 74 7/24/011234 17 7/25/01

CustomerID First Last15 Connie Fisher16 Rosie Wade17 Carly Embry

Sale Customer

QueryJoin

Dataentry Data

display


24/37

24

LabelText Box

Option Group(single response)

Basic Form Controls

Combo Box(click arrow to open)

List Box(always open)

CommandButton


25/37

Complex Form Controls

CommonTabGridCalendar

25

Tab

Calendar

augeSliderSpin Box

Additional

PurchaseCreate your own (C++)

Grid

Gauge Slider Spin box


26/37

A form can contain 2 types of

pictures:-Background pictures

Pictures that are use only for

26

Employee

Name: Che Zhang

ID: 3354Phone: 222-111-1524

. . .

Pictures

aesthetic purposes

Pictures stored as dataPictures that are bound to a datacolumn and stored in the

database.A picture can be stored in adatabase as an object

Photo:


27/37

A query can be built

to generate data thatcan be represented asa chart.

27

Sale 1

Sale 2

Merchandise

Merchandise

Animal

Animal

Charts

Usually restricted tonumeric data

Charts can be

displayed on formsand linked to otherforms to see its raw

data

Sale 3 Merchandise

Animal

Total Sales

Merchandise

Animals


28/37

Avoid relying on formsSet integrity conditions in tabledefinitionsBe sure to set referential integrity(relationships)

Use forms to make it easy to enter

ControlsSecurity rightsData formats

Data entryRound-off

Selectivit

28

Data Integrity

quality dataCombo/list boxesMenusPop-up formsTies to related formsData transfer across formsComputationsError checking & trapping

VisibleEnabled & LockedExample: no productionchange after item is sold.

User assistanceTool tipsStatus barMenuHelp--context sensitive


29/37

29

Reports are used to present data and

summarized dataUnlike forms reports do not have controls tocollect data or manipulate data at runtime

Reports

an manipu ate ata at esign time

Main strengths of reports1. Reports can easily handle multiple pages of output2. Reports can combined both detailed and summarized

data


30/37

Report usage/user needs.Report layout choices.

TabularColumns/SubgroupsCharts/graphs

Security controlsDistribution listUnique numberingConcealed/non-printed dataSecured printers

30

Report Design Issues

Paper sizes.Printer constraints.How often is it generated?Events that trigger report?How large is the report?Number of copies?Colors?

Transmission limitsPrint queue controls

Output concernsTypefaces

ReadabilitySizeUser disabilities


31/37

31

Report Type: Tabular


32/37

32

Report Type: Label


33/37

Column.

Column with groups.

33

Report Types: Group or Subtotal


34/37

Report Header

Page Header

Group Header1

34

Report Header

. . .Detail

. . .Group Footer2

Group Footer1Page FooterReport Footer


35/37

Report Header

Title pages that are printed one time for entire report.Page Header

35

Report Layout / Common Use

every page.Group Header

Data for a group (e.g., Order) and headings for thedetail section.

DetailInnermost data.


36/37

Group Footer

Subtotals for the group.Page Footer

36

Report Layout/Common Use .. cont.

r n e a e o om o every page--page o a s orpage numbers and notes.

Report FooterPrinted one time at the end of the report. Summarynotes, overall totals and graphs for entire data set.


37/37

Summary

Today lesson you have learned how to:

Explain the purpose of forms and reports.Explain the types of forms and reports.Ex lain the basic human factors involved when

37

designing forms.Explain the controls to be used on forms.Describe the basic and complex components of forms.

Describe the overall structure of reports.

Documents

Database SSK3408-Chapter04