Breaking Out of the Box Oracle Forms

8/3/2019 Breaking Out of the Box Oracle Forms

1/174

Breaking Out of the BoxOracle Developer/Forms

for Experienced Rdb Developers

Cheryl P. JalbertThomas H. Musson Jeffrey S. Haidet

Keith W. Hare Jeffrey S. Jalbert

JCC Consulting, Inc. Granville OH 43023


2/174


3/174

Copyright 1998, JCC Consulting, Inc., All rights reserved.Confidential and proprietary to JCC Consulting, Inc. 3

Scheduleq EOUG: Hints and Kinks 8:30 - 9:15

Designed for those who know Developer orwho know Rdb

Collection of topicsq Rdb Forum: Breaking Out of the Box

13:00 - 15:15

Designed for people with Rdb experience

Quick introduction to Developer/Forms Specifics of using Developer with Rdb

Additional advanced topics

Discussion of the value that you can expect from using

Developer/Forms with Rdbq Rdb Forum: Discussion / Q & A

15:15 - 16:00

q Rdb Forum: Demos ?


4/174


Assumptions

q You have one or more existing Rdb databases.

q You lack a satisfactory GUI (Graphical UserInterface).

q You need to provide either a data warehouse /decision support system or you need to add some of

those capabilities to your existing TP applications.q Your existing UI took time to create and takes time to

enhance.

q You need a quick success. Time is an importantfactor.

Does this sound familiar?


5/174


Configurations and Choices

q Configurations

Traditional

Classic Client/Server

Multi-dimensional Client/Server

New Ways with Terminals

Windows Terminals

Thin Clients on the Web

Other

q Software Pieces and Parts

q Design Choices


6/174


TraditionalRemember main frames and terminals?


7/174


Classic Client/ServerThe client provides the user interface.

The server provides the database.


8/174


Multi-dimensional Client/ServerA client relies on a server to provide a resource.

ProductionDB Server

TrainingDB Server

File & Print Serverfor Remote Office

Mapping

Application Server

for Remote Office Clients


9/174


New Ways with TerminalsHow well do you remember terminals?

You can produce forms for

terminals & PCs from the same

development project.


10/174


Windows TerminalsNew wrinkle on an old scheme that centralizes

management


11/174


Thin Clients on the Web


12/174


Configuration for Some SessionsDB Server

Map Server

Client


13/174


Background for Your Choicesq What are your requirements?

q What are your resources?


14/174


Dumb Terminals as Your Choiceq Advantages

You canuse Oracle Developer with terminals.

You candevelop forms that use the same code for windowsor dumb terminals on VAXes.

Oracle Developer compares well with other forms packagesfor dumb terminals.

Terminals provide centralized management. You may have a set of terminals in place.


15/174


Dumb Terminals as Your Choiceq Disadvantages

Oracle has shown no interest in keeping terminal support

current. You will be stuck with Version 1.3.2 for your workwith terminals.

Developing for dumb terminals is much more tedious.

Dumb terminals lack real estate.

Dumb terminals do not supportq icon buttons

q pull-down menus

q color changes for subtle clues

q graphicsq integration with newer technologies

q navigation with a mouse

q pop-up alerts


16/174


Windowing Devicesq Advantages

Newer technology

q

Oracle development is ongoing.q Components that can be integrated are hot items.

Prototyping a form for user review is quick and easy.

Fewer and fewer people need to be taught the basics of how

to use the application that you develop. Use of your application is supported by

q icon buttons

q pull-down menus

q color changes for subtle clues

q graphics

q integration with newer technologies

q navigation with a mouse

q pop-up alerts


17/174


Windowing Devicesq Disadvantages

Costs may be higher

q because you have terminals in placeq because you have PCs in place and cant control the

maintenance costs

Your application may be better suited to terminal styles

q You may need to disable mouse navigation for heads downdata entry.


18/174


Client/Server Choices Five Tier Model

User

Interface Data

Applicatn.

Logic

Interfc.

Logic

Data

Logic

Client

Server

Thic k Clie n t

ThinClient


19/174


20/174


Translating Oracles New Namesq Oracle Developer 2000 V2.x

Forms V5.0

Reports V3.0 Graphics V3.0

q Now, its Oracle Developer (without the 2000).

q

Oracle Developer V6.0 is out. Forms V6.0

Reports V6.0

Graphics V6.0


21/174


Software Pieces and Partsq Database

Oracle 7 or 8

Rdb (Use Version 7.0 or higher to use SQL*net.)q User Interface

Developer Forms (Version 5.0.6.10.0 is out.)

For VMS terminals (Developer V1.3.2, Forms V4.5.7.1.6)

q Data Transport Mechanism SQLNet (Preferred)

ODBC (Required for earlier versions or non-Oracle db.)

q Operating Systems VMS

NT

W95


22/174


Production Systems PrerequisiteSoftware

q On Client

Developer

SQL*net SQL*net network adapter [e.g. TCP/IP]

Operating System Network [e.g. W 95 or W/NT]

q

On Server Network Software, e.g. UCX/DECnet

Native Connect (Part of SQL Services)

SQL*net. (This is installed with SQL Services ifnot already present on system.)

Rdb V7.0


23/174


Other Software Pieces and Partsq Other data stores

q Other clients

q Other operating systems

q ActiveX controls

q Batch processing

q eXcel and such

q Icon editors

q Documentation support


24/174


Design Choicesq Style(s) of use

unanticipated queries

heads down data entry query only

access limited

audited

q Styles of presentation

toolbar

menus

buttons hot keys

graphics

exceptions


25/174


26/174


27/174


28/174


and Another Form ...

Several things are obscured here to

avoid revealing company confidentialdata, but the thing of interest to you is

this button.


29/174


30/174


31/174


Introductionq Parts that you will produce

q Tools that you will use

q First steps

q Special requirements for Rdb

q The user view and default functionality

q Standards and how to make things easy

q Pointers to intermediate topics


32/174


Open the Forms Builder


33/174


Open the Form Builder


34/174


35/174


What You See First(if you choose Build a new form manually)


36/174

Copyright 1998, JCC Consulting, Inc., All rights reserved.

Confidential and proprietary to JCC Consulting, Inc. 36

Module, Block, Canvas, Window

Well

discuss

thesetopics

in this

section.


37/174



Components: Modules and Blocksq Module

Forms file

FMB extension Generates an FMX extension, when generated or run, (ifyou

have the compile before running option checked.)

q Block

Blocks for tables

Blocks for buttons

Blocks for a toolbar

Blocks for other types of things

One or many blocks per module

Displayed in frames


38/174


39/174


40/174


41/174



Your Tools: Properties Palette


42/174



Your Tools: Layout Editor


43/174


44/174



The Developers Tools in an Example


45/174



Examining the Object NavigatorThe boxes on the left

enable you to see

more or less detail inthe navigator. These

have the following

meaning:q Expanded

q Unexpanded (butsomething toexpand

q Nothing to expand


46/174


47/174



Close-up of the Property Palette

We see that the

payment canvasq is displayed

q is displayed in the

payment_windowq is 505 X 149

Some characteristicsare not set at all.


48/174


49/174


50/174


51/174



Using the Wizards

Recommendation: Use the Data Block Wizard.

This form will pop-up, when you add a block.


52/174



Creating a Block Based on a Table


53/174


54/174


55/174



Browsing the MetadataIf youve asked to browse for a table, you will next see

this form.


56/174



Rdb Specifics for Browsing the Metadataq Select Other users, as well as Current user.

Oracles other database includes a concept of subschemas.The Current user default assumes that you only want to seethe sub-schema built for you. In the Rdb context, therefore,you need to make certain that you get everyones tables.

q Select Views, if you need those, too.

Heads up: If any of your tables use a table or column name ofover 30 characters (or, in some cases, over 29 characters) youwill want to create a view that uses shorter names and use theview with Developer 2000.


57/174



Selecting Your Table or View

q Use the Findwindow tosearch for your

table.q Use the % as a

wild card in theFind window.

q OrScroll to thetable that youwant.


58/174



Selecting Your ColumnsSelect columns by

q Selecting them in

the available list anddragging them to theDatabase Items list

q OrSelecting each

and pressing >q OrPressing >> to

move them all.

Include the key.(You will not have to

display it.)


59/174



Choosing the Layout Wizard


60/174



Beginning the Layout Wizard


61/174



Choosing the Canvas

q Create a new

canvas

q Oruse anycanvas in this

module.


62/174



Setting Up the Block

q Display all of

the columnsthat youincluded in the

block.q Orleave some

of them out.


63/174



More Wizardly Choices

Default choiceswork well, here.


64/174

Copyright 1998, JCC Consulting, Inc., All rights reserved.Confidential and proprietary to JCC Consulting, Inc.

64

Choosing Your Layout Style

q Form layout stylearranges columnsvertically.

q Tabular layout stylearranges columnshorizontally andworks well withmultiple rows.


65/174


65

Other Choices

q The Frame Title(block title) isdisplayed above thedisplay of the fields.(You can leave it

blank.)q If you use 1 as the

number of RecordsDisplayed, the other

two fields should beleft as the defaults.


66/174


66

Finishing the Layout Wizard


67/174


67

The Layout Wizard and Framesq Frames

Display container for a block

Displayed on a canvas Find it as an item under block in the Object Navigator

q Issues

With the V2.0 Layout Wizard, you may need to adjust the

dimensions of the frame after you receive exceptionmessages from the Wizard. A large number of fields or anyfields with a large number of characters may causedifficulties.

If your fields spontaneously rearrange themselves!, it isbecause the frame property Update_layout is set toautomatically (instead of manually) in the Property Palette.


68/174


68

Examining the Results


69/174


69

Changing the DefaultsThere are several ways to change the default result.

q With a free-hand approach to the Layout Editorq Using the Pull-down Menus for the Layout Editor

q Changing properties in the Property Palette

q Using a combination of the Layout Editor Toolbar andfree-hand

q Changing navigation order in the Object Navigator


70/174


70

Free-Hand in the Layout Editor

q

Click on the canvas anddrag it to re-size it.

q Select all of the fields andlabels and move them.

q Line up individual items.

q Add text.

q Add a rectangular frame.

q Add a button or otherfeature.

You can select and change things directly in the layout

editor. For example,


71/174


71

Menus for the Layout EditorThe Menus for your development screen are context

sensitive. Investigate which menu items are available

with the Layout Editor. For example,q Arrange

Align

Group

q Format

Font


72/174


72

For Example: Alignment


73/174


74/174


74

For Example: FontsIf you

q select all of the name fields

q choose Format, Font


75/174


75

Fonts

You canmake all

the usual

font

changes.

Changing the Form


76/174


76

with the Properties PaletteChanges that you can make in the layoutwith the

properties palette include:

q Rearranging the column layouts

q Changing labels

q Changing fontsq Changing query criteria


77/174

Using the Property Palette to


78/174


78

Change the Layoutq Check on the position

and size of a field thatyou would like to useas a starting point.

q Arrange other fieldsrelative to this one.

Changing Multiple Things at Once


79/174


79

Changing Multiple Things at Once

Sometimes, you will

want to change

multiple fields at once.Here, the several lines

of the address are

selected. The **** for

prompt shows that the

fields selected have

different values for this

property.

Editing Prompts


80/174


80

d t g o pts

When you edit a prompt and then press return, you

will get this pop-up. You can then edit further.

Changing Other Defaults


81/174


81

g g

For text fields, one of the things

that you may want to change is

the NO default for

Case Insensitive Query.

The Layout Editor Toolbar


82/174


82

y

The Layout Editor Toolbar offers shortcuts to change

the defaults.

Adding Other Text


83/174


83

g

Use the Text button to add text.

(Double click to add, or edit, several text items.)

Adding Color


84/174


84

g

Color for

q Fill

q Line

q Text

Rearranged Form


85/174


85

View of the form in the layout editor. There are visible

and invisible changes to make yet.

Follow Naming Standards


86/174


86

Type here and press enter

to rename here

and here.


87/174

Window Size


88/174


Changing thewindow size

to fit the canvasis optional.

Determining Navigation Order


89/174


Use the Object Navigator todetermine the order in which

the fields are visited.

q Drag and drop so thatfirst_name is the first field.

q Etc.

Special Considerations for Rdb


90/174


q The special tuning that was required to useDeveloper 2000/Forms with Rdb is less necessarystarting with Version 7.0 of Rdb and Version 5.0 ofForms.

q With some versions, you will still need to understandthe special requirements.

q Satisfying the special requirements makes goodexamples of how to manipulate Forms.

q Examining these issues is an interesting look at howRelational Database Management Systems differ.

Changes to Accommodate Rdb


91/174


The property palette defaults are not correct for Rdb for:

q Pre-Version 7 of Rdb

Pre-Version 5 of Forms When using ODBC

q In some additional cases for best performance

We will discuss

q Each issue

q Reason for each issue

q Current status of each issue

Required Changes for Rdb

with Some Product Versions


92/174


with Some Product Versionsq Module

Savepoint Mode = False (Default is True in earlier versions.Property is not shown in Forms 5.)

q Block Enforce Primary Key = Yes (Default is No.)

Key Mode = Nonupdatable (Default is Unique for pre V5 orAutomatic for post V5.)

Locking Mode = Delayed (Default is Immediate for pre V5 orAutomatic for post V5.)

q Items

Primary Key = Yes, for one or more items (Default is No.) Maximum Length and Query Length must be one character

longer than in the database, ifusing ODBC in someversions.

Module Level Changes for Rdb


93/174


q Oracle7 supports savepoints for sub-transactions.

q Oracle Rdb does not.

q Set the modules Savepoint = FALSE, if you areusing

Developer/2000 prior to Release 2.0, which is also

Oracle Forms prior to Release 5.0

Block Level ChangesThese still apply:


94/174


These still apply:

q Enforce Primary Key (formerly, Primary Key)

Oracle 7 uses internally generated synthetic keys.

Oracle Rdb relies on DBA defined primary keys. For Rdb, set the block property Enforce primary key = Yes.

q Key Mode

Oracle 7 uses key mode unique for the system generated keys.

Oracle Rdb requires key mode updatable or non-updatable.

JCC uses non-updatable for Rdb.

(Continued)

Block Level Changes


95/174


This one only applies if you are using products pre-V7

of Rdb:

q Locking Mode By default, D2000 uses locking mode immediate, which

takes an exclusive lock as soon as the user starts typing.

For concurrency, use locking mode = delayed, which takes

the lock when the user saves. Both locking modes re-readand compare.


96/174

Module Level Changes

in the Property Palette


97/174


in the Property Paletteq Savepoint Mode = False

Notice that there is

NO illustration of this

for Forms 5 &

Developer 2000 V2.

Block Level Changes



98/174


in the Property Paletteq Enforce

Primary Key =Yes (Default is

No.)

q Key Mode =Nonupdatable

(Default isAutomatic.)

q Locking Mode= Delayed

(Default isAutomatic.)

Values of

Automatic

work withoutchanges.

Item Level Changes



99/174


in the Property Paletteq Primary Key =

Yes, for one ormore items(Default is No.)

q MaximumLength and

Query Lengthmust be onecharacterlonger than in

the database,ifusing ODBC.

You, Developer 2000/Forms, & Rdb


100/174


q Improvements in the software have made the Rdbconnection more transparent.

q There is still value in defining table keys.

q There is still value in understanding the issues.


101/174

Default Menus and Toolbar


102/174


q Pull-down menus

q Toolbar

q More ...

Querying

q Enter Query Specifying the query criteria:


103/174


q Enter Query

q Execute Query

q Count Hits

q Cancel

Specifying the query criteria:

q Any subset of the fields available

q Exact matches

q Wildcarding

q

Query retrieval bygroups of rows

Help


104/174


Choosing Help on

the default Help

menu displays the

property palette

information on the

item selected.

Hot KeysChoosing Keys


105/174


on the Help menu

displays this form.

Notice

q F1 is Help

q F7 is EnterQuery

q F8 is ExecuteQuery

q You can scrollfor more.

Printing


106/174


q Since many forms arewider than tall, printing in

landscape mode isusually best.

q D2000 defaults to portrait.

If you use this feature well, it seems like a free report.


107/174

Standards and Inheritance

This section introduces how an application


108/174


q Property classes (domains)

q Visual Attributesq Program Units

q Object Libraries

q Property Classes vs. Object Librariesq Templates

This section introduces how an applicationdeveloper can use modern software engineertechniques from within an Oracle Developer

application.

Component Software

q Baby Steps


109/174


q Baby Steps

Create generic functionality

Gradually refine functionality as needed for applications

Maintenance made easier

Level 1 Level 1 Level 1

Level 2 Level 2

Application

Refine

Refine

Building Blocks for Software Development


110/174


Interface

(Visual Attributes)

Logic

(Program Units)

Easy to Use,

MaintainableApplication

Standards

(Property Classes)


111/174


112/174


113/174

Program Units

q Program units are PL/SQL procedures and functions


114/174


g pthat are encompassed in a form

q Used for tasks that could potentially occur multipletimes in a single form

q Example:

JCCs GET_ID functionality

Override Developers default assembly of the query Population of default values when creating a new record

Etc.


115/174

Property Class Module

If using a pre-Developer 2.x release


116/174


JCC recommends:

q Create a separate module for

property classesq Copy the property classes from

this module to other formmodules, as a subclass

q Ensure all form modulesreference the same propertyclass module

Enforces a single point of codemaintenance (software buildingblock)


117/174


118/174

Property Class Module vs. Object Librariesq Property Classes

Can contain property classes, but not all items in pre-Developer 2.xcould be subclassed (Program units)


119/174


could be subclassed (Program units)

Must have Property Class module open in order to drag in and dropproperty classes to make them available to a form

Only way to implement inheritance pre-Developer 2000 Release2.0

q Object Libraries

Can contain ALL types of objects that do not have to be copied(subclassed) into forms in ordered to be referenced

q This includes Property Classes, Program Units, Windows, Canvases,Visual Attributes, Items, Toolbars, etc.

The Object Library opens automatically when the Forms Designer

is opened making objects immediately available.

New feature in Developer 2000 Release 2.0 that truly implementsinheritance (linked during compilation)

119


120/174


121/174


122/174


123/174


124/174

Advanced Topics


125/174

Teaching the Application to Sing


126/174


127/174

Developer Exceptions

q Oracle has several pre-defined, named exceptions

CURSOR ALREADY OPEN


128/174


CURSOR_ALREADY_OPEN

DUP_VAL_ON_INDEX

INVALID_CURSOR PROGRAM_ERROR

etc - see the PL/SQL Users Guide and Reference for acomplete list

q Each exception has a severity level associated with it Valid levels are 0, 5, 10, 15, 20, 25

0 is least severe

25 is most severe


129/174


130/174


131/174


132/174


133/174

Recording Client Exceptions

q Why record exceptions?

User: I just got an error.


134/174


j gIS: What was the error?

User: It said something about convertingIS: What? What screen are you on?User: Screen XIS What were you doing?User Trying to open a new account.

ooo

Any questions?

Recording Client Exceptions

q Problem: Need to record client exceptions

q Problem: Need to be able to access the exception


135/174


q ob e eed to be ab e to access t e e cept odata without having access to the machine

q Problem: Need to capture exceptions even whendevelopers forget to implement exception handling

q Solution: A procedure that logs client exceptions on

the server and use a default exception handler Records client exceptions

Output is on server

Catches all exceptions


136/174

On-Error Trigger

q On-Error/*** Built-in: ERROR_CODE,ERROR_TEXT,ERROR_TYPE** Example: Reword certain FRM error messages by checking


137/174


Example: Reword certain FRM error messages by checking** the Error_Code in an ON-ERROR trigger** Trigger: On-Error*/DECLAREerrnum NUMBER := ERROR_CODE;errtxt VARCHAR2(80) := ERROR_TEXT;errtyp VARCHAR2(3) := ERROR_TYPE;

BEGIN/*** Log the message are where it occurred.**** Print the Normal Message that would have appeared.

*/comc.record_exception(comc.form_event,Property class ||errtyp||-||TO_CHAR(errnum)||': ||errtxt||' on '||:system.trigger_item);

Message(errtyp||'-'||TO_CHAR(errnum)||': '||errtxt||' on '||:system.trigger_item);end;


138/174

What We Will Discuss

q How D2K calls a stored procedure

q Calling an Rdb Stored Procedure


139/174


q Example

q We will not discuss configuration management ofstored procedures

How D2K Calls A Stored Procedure

q The traditional method for calling a stored procedurefrom D2K is a simple, in-line call:


140/174


beginprocedure_to_call();

end;

q Works for Oracle 7/8 procedure/data sources

Calling An Rdb Stored Procedure

q The first implementation of SQL*Net for Rdb did notinclude stored procedure support


141/174


q We needed to use stored procedure calls to allow

multiple platforms access to the same codeq Necessity is the mother of invention

Benjamin Franklin

q Use Forms_DDL calls Forms_DDL(procedure_to_call());

DDL means Data Definition Language


142/174

Example - Exception Reporting Routine

q Problem: Capture client messages on the server

q Problem: Must be able to record events outside of thef i


143/174


context of a transaction

q Answer: Use a stored procedure that does nodatabase work

Short compilation and execution time

Outside of transaction contexts

Messages are logged on the server and can be culled on afrequent basis


144/174


145/174


146/174


147/174


148/174


149/174


150/174


151/174


152/174


153/174


154/174


155/174

Configuration Management

q You need to take the same care that you do withmain frame applications.

q Our project consists of


156/174


p j

5 or more developers working with Developer/Forms almost 300 modules

q We use MicroSofts Visual Source Safe

to provide a library of all the modules

q forms

q icons

q DLLs

q common libraries

to ensure that we arent all working at cross purposes


157/174


158/174


159/174


160/174


161/174


162/174


163/174


164/174


165/174

Developer Defaults

q Advantages of built-in defaults

Provides a starting point

Many are well chosen


166/174


q Disadvantages of built-in defaults Have changed between releases

May not meet your needs

q Building your own defaults

Use the standardization tools

Avoid unnecessary changes from

q Oracle Developer standards

q Industry standards


167/174


168/174


169/174


170/174

Questions?

Cheryl P. Jalbert [email protected]

Jeffrey S. Jalbert [email protected]

Keith W. Hare [email protected]

Th H M @j


171/174


Thomas H. Musson [email protected] S. Haidet [email protected]

Phone (740)587-0157

Web: www.jcc.comList Server: RdbD2K

To subscribe to the list server:

Send mail to [email protected].

Include subscribe RdbD2K in the body of your message.

Questions?


172/174



173/174


174/174

Breaking Out of the Box Oracle Forms

Documents

Transcript of Breaking Out of the Box Oracle Forms