Breaking Out of The Box Oracle Forms

Breaking Out of the Box Oracle Developer/Forms for Experienced Rdb Developers
Cheryl P. Jalbert
Thomas H. Musson Jeffrey S. Haidet Keith W. Hare Jeffrey S. Jalbert
JCC Consulting, Inc. Granville OH 43023
Abstract
Users of Oracle Rdb have sometimes expressed frustration with whatever forms products they were using with Rdb. Consequently, when someone suggests huge advantages from using the Oracle toolset, many Rdb experts are dubious. This session will address some of your questions and go well beyond those questions into the hints and kinks of successfully combining Oracle Rdb and Oracle Forms to empower users, significantly enhance developer throughput and improve your flexibility relative to hardware platforms. The attendee will understand the management tasks associated with using Oracle Developer with Oracle Rdb.
Copyright 1998, JCC Consulting, Inc., All rights reserved. Confidential and proprietary to JCC Consulting, Inc.
Schedule
q
EOUG: Hints and Kinks

8:30 - 9:15 Designed for those who know Developer or who know Rdb Collection of topics
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 Rdb
q q
Rdb Forum: Discussion / Q & A

15:15 - 16:00
Rdb Forum: Demos ?

Assumptions
q q
You have one or more existing Rdb databases. You lack a satisfactory GUI (Graphical User Interface). 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. Your existing UI took time to create and takes time to enhance. You need a quick success. Time is an important factor. Does this sound familiar?
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 q
Software Pieces and Parts Design Choices
Traditional
Remember main frames and terminals?
Classic Client/Server
The client provides the user interface. The server provides the database.
Multi-dimensional Client/Server
A client relies on a server to provide a resource.
Production DB Server
Training DB Server
File & Print Server for Remote Office Mapping Application Server for Remote Office
Clients
New Ways with Terminals

How well do you remember terminals?
You can produce forms for terminals & PCs from the same development project.
Windows Terminals
New wrinkle on an old scheme that centralizes management
10
Thin Clients on the Web
11
Configuration for Some Sessions

DB Server Map Server
Client
12
Background for Your Choices

q q
What are your requirements? What are your resources?
13
Dumb Terminals as Your Choice

q
Advantages
You can use Oracle Developer with terminals. You can develop forms that use the same code for windows or dumb terminals on VAXes. Oracle Developer compares well with other forms packages for dumb terminals. Terminals provide centralized management. You may have a set of terminals in place.
14
Dumb Terminals as Your Choice

q
Disadvantages
Oracle has shown no interest in keeping terminal support current. You will be stuck with Version 1.3.2 for your work with terminals. Developing for dumb terminals is much more tedious. Dumb terminals lack real estate. Dumb terminals do not support
q q q q q q q
icon buttons pull-down menus color changes for subtle clues graphics integration with newer technologies navigation with a mouse pop-up alerts
15
Windowing Devices
q
Advantages
Newer technology
q q
Oracle development is ongoing. 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 q q q q q q
icon buttons pull-down menus color changes for subtle clues graphics integration with newer technologies navigation with a mouse pop-up alerts
16
Windowing Devices
q
Disadvantages
Costs may be higher
q q
because you have terminals in place because you have PCs in place and cant control the maintenance costs You may need to disable mouse navigation for heads down data entry.
Your application may be better suited to terminal styles

q
17
Client/Server Choices Five Tier Model

Client Server
User Interface Interfc. Logic Applicatn. Logic Data Logic
Data
Thin Client
Thick Client
18
Your Choices
q
Thin Clients
WEB Can minimize network traffic. Can reduce systems work (by ignoring the systems work for the client).
Thick Clients
Use the database to address access issues. Use the database to audit. Use the database to ensure consistent results. Can maximize reusable components. Can enhance standardization. Can minimize network traffic. Can reduce systems work.
19
Translating Oracles New Names

q
Oracle Developer 2000 V2.x

Forms V5.0 Reports V3.0 Graphics V3.0
q q
Now, its Oracle Developer (without the 2000). Oracle Developer V6.0 is out.
Forms V6.0 Reports V6.0 Graphics V6.0
20
Software Pieces and Parts

q
Database
Oracle 7 or 8 Rdb (Use Version 7.0 or higher to use SQL*net.)
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)
Data Transport Mechanism

SQLNet (Preferred) ODBC (Required for earlier versions or non-Oracle db.)
Operating Systems
VMS NT W95
21
Production Systems Prerequisite Software On Client

Developer SQL*net SQL*net network adapter [e.g. TCP/IP] Operating System Network [e.g. W 95 or W/NT] On Server Network Software, e.g. UCX/DECnet Native Connect (Part of SQL Services) SQL*net. (This is installed with SQL Services if not already present on system.) Rdb V7.0
22
Other Software Pieces and Parts

q q q q q q q q
Other data stores Other clients Other operating systems ActiveX controls Batch processing eXcel and such Icon editors Documentation support
23
Design Choices
q
Style(s) of use
unanticipated queries heads down data entry query only access limited audited toolbar menus buttons hot keys graphics exceptions
Styles of presentation

24
An Example
25
Example Form
Notice the Menus & the Toolbar & the special buttons at the bottom for audit or notes or other things.
26
Another Example Form
Data is erased here for non-disclosure reasons.
The dark blue background is a clue to the user that this isnt part of the query area.
27
and Another Form ...
Several things are obscured here to avoid revealing company confidential data, but the thing of interest to you is this button.
28
Integrated from Another Technology
29
Developing Forms -The Basics & Default Functionality
Getting Started Developing Forms
Introduction
q q q q q q q
Parts that you will produce Tools that you will use First steps Special requirements for Rdb The user view and default functionality Standards and how to make things easy Pointers to intermediate topics
31
Open the Forms Builder
32
Open the Form Builder
33
Getting Started
q
Examine the new front piece provided by Oracle.

Use the Help provided. Use the wizards.
Choose a starting point.

Use the Data Block Wizard OR Open an existing form OR Build a form based on a template OR Build a new form manually.
Click OK.
(We will choose Build a new form manually in order to look, first, at some of the tools that you will use.)
34
What You See First

(if you choose Build a new form manually)
35
Module, Block, Canvas, Window
Well discuss these topics in this section.
36
Components: Modules and Blocks

q
Module
Forms file FMB extension Generates an FMX extension, when generated or run, (if you have the compile before running option checked.)
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
37
Components: Canvases and Windows

q
Canvas
Display surface for blocks (in frames) and text. Each block must be assigned to a canvas. A canvas can include many blocks. One or more canvases per module.
Window
View of a canvas or many canvases. Users view of what youve created. Windows can be re-sized and moved by the user and, also, programmatically.
38
Your Tools: Tools Menu
39
Your Tools: Object Navigator
40
Your Tools: Properties Palette
41
Your Tools: Layout Editor
42
Developers Primary Tools

q
Object Navigator
Lists each different type of object and the objects in that type for each module that is open for development work. Main work space Details can be expanded or contracted on the display
Property Palette
Easy way to change the characteristics of objects. Not all characteristics will be of interest for all objects.
Layout Editor
Editor for the form presentation. Where graphics and text is added. Easy place to add buttons and extra fields.
43
The Developers Tools in an Example
44
Examining the Object Navigator

The boxes on the left enable you to see more or less detail in the navigator. These have the following meaning: q Expanded q Unexpanded (but something to expand q Nothing to expand
45
Closeup of the Object Navigator

In this module, we see q three data blocks q two canvases q two windows There are also some q triggers q attached libraries q LoVs q property classes q record groups
46
Close-up of the Property Palette

We see that the payment canvas q is displayed q is displayed in the payment_window q is 505 X 149 Some characteristics are not set at all.
47
Close-up of the Layout Editor

The layout editor supports arrangement of the canvas. q This layout shows some of the styles chosen for the application used as an example
q q
the title decorative frame (blue rectangle)
q q
buttons colors
q q
alignment fonts
q q
The tools for changing things are on the left side. The canvas is shown selected.
48
Your Tools
The tools work together. In the example, the payment canvas is selected for q Object Navigator q Property Palette q Layout Editor
49
Using the Object Navigator to Add a Block
To add one of the objects q select that object type q press the green +
50
Using the Wizards

This form will pop-up, when you add a block.
Recommendation: Use the Data Block Wizard.

51
Creating a Block Based on a Table
52
Form for Choosing the Table
Press Browse to see the list of tables and views
Or type in the name.
53
Connecting to the Database

The first time that you try to read from the database (whether you are reading data or metadata), you will need to connect to the database. The Connect form will pop up automatically. Fill it in appropriately.
54
Browsing the Metadata

If youve asked to browse for a table, you will next see this form.
55
Rdb Specifics for Browsing the Metadata

q
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 see the sub-schema built for you. In the Rdb context, therefore, you need to make certain that you get everyones tables.
Select Views, if you need those, too.

Heads up: If any of your tables use a table or column name of over 30 characters (or, in some cases, over 29 characters) you will want to create a view that uses shorter names and use the view with Developer 2000.
56
Selecting Your Table or View
Use the Find window to search for your table. Use the % as a wild card in the Find window. Or Scroll to the table that you want.
57
Selecting Your Columns

Select columns by q Selecting them in the available list and dragging them to the Database Items list q Or Selecting each and pressing > q Or Pressing >> to move them all. Include the key. (You will not have to display it.)
58
Choosing the Layout Wizard
59
Beginning the Layout Wizard
60
Choosing the Canvas

q
Create a new canvas Or use any canvas in this module.
61
Setting Up the Block

q
Display all of the columns that you included in the block.
Or leave some of them out.
62
More Wizardly Choices
Default choices work well, here.
63
Choosing Your Layout Style
Form layout style arranges columns vertically. Tabular layout style arranges columns horizontally and works well with multiple rows.
64
Other Choices
q
The Frame Title (block title) is displayed above the display of the fields. (You can leave it blank.) If you use 1 as the number of Records Displayed, the other two fields should be left as the defaults.
65
Finishing the Layout Wizard
66
The Layout Wizard and Frames

q
Frames
Display container for a block Displayed on a canvas Find it as an item under block in the Object Navigator
Issues
With the V2.0 Layout Wizard, you may need to adjust the dimensions of the frame after you receive exception messages from the Wizard. A large number of fields or any fields with a large number of characters may cause difficulties. If your fields spontaneously rearrange themselves!, it is because the frame property Update_layout is set to automatically (instead of manually) in the Property Palette.
67
Examining the Results
68
Changing the Defaults

There are several ways to change the default result.
q q q q
With a free-hand approach to the Layout Editor Using the Pull-down Menus for the Layout Editor Changing properties in the Property Palette Using a combination of the Layout Editor Toolbar and free-hand Changing navigation order in the Object Navigator
69
Free-Hand in the Layout Editor

You can select and change things directly in the layout editor. For example, q Click on the canvas and drag it to re-size it. q Select all of the fields and labels and move them. q Line up individual items. q Add text. q Add a rectangular frame. q Add a button or other feature.
70
Menus for the Layout Editor

The 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
71
For Example: Alignment
72
Alignment
Choose how you want the selected fields aligned q horizontally q vertically You can then group the items.
73
For Example: Fonts

If you q select all of the name fields q choose Format, Font
74
Fonts
You can make all the usual font changes.
75
Changing the Form with the Properties Palette

Changes that you can make in the layout with the properties palette include:
q q q q
Rearranging the column layouts Changing labels Changing fonts Changing query criteria
76
Examining the Properties for a Column
77
Using the Property Palette to Change the Layout

q
Check on the position and size of a field that you would like to use as a starting point. Arrange other fields relative to this one.
78
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.
79
Editing Prompts
When you edit a prompt and then press return, you will get this pop-up. You can then edit further.
80
Changing Other Defaults
For text fields, one of the things that you may want to change is the NO default for Case Insensitive Query.
81
The Layout Editor Toolbar
The Layout Editor Toolbar offers shortcuts to change the defaults.
82
Adding Other Text

Use the Text button to add text. (Double click to add, or edit, several text items.)
83
Adding Color
Color for q Fill q Line q Text
84
Rearranged Form
View of the form in the layout editor. There are visible and invisible changes to make yet.
85
Follow Naming Standards
Type here and press enter to rename here and here.

86
Other Naming Issues
Notice window name.
When you change the window name, Developer 2000 does not lose the association between the window and the canvases displayed in the window. Expect this same flexibility in other name changes.
87
Window Size
Changing the window size to fit the canvas is optional.
88
Determining Navigation Order
Use the Object Navigator to determine the order in which the fields are visited. q Drag and drop so that first_name is the first field. q Etc.
89
Special Considerations for Rdb

q
The special tuning that was required to use Developer 2000/Forms with Rdb is less necessary starting with Version 7.0 of Rdb and Version 5.0 of Forms. With some versions, you will still need to understand the special requirements. Satisfying the special requirements makes good examples of how to manipulate Forms. Examining these issues is an interesting look at how Relational Database Management Systems differ.
90
Changes to Accommodate Rdb

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
91
Required Changes for Rdb with Some Product Versions

q
Module
Savepoint Mode = False (Default is True in earlier versions. Property is not shown in Forms 5.)
Block
Enforce Primary Key = Yes (Default is No.) Key Mode = Nonupdatable (Default is Unique for pre V5 or Automatic for post V5.) Locking Mode = Delayed (Default is Immediate for pre V5 or Automatic for post V5.)
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, if using ODBC in some versions.
92
Module Level Changes for Rdb

q q q
Oracle7 supports savepoints for sub-transactions. Oracle Rdb does not. Set the modules Savepoint = FALSE, if you are using
Developer/2000 prior to Release 2.0, which is also Oracle Forms prior to Release 5.0
93
Block Level Changes

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)
94
Block Level Changes

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-read and compare.
95
Item Level Changes

q
This still applies: For attributes that are part of the key
Set Primary key = Yes To enforce the primary key, Developer 2000 must know what the key is.
If using ODBC: for all items

Set Maximum length to usual length plus one. Set Query length to usual length plus one. ODBC needs a character for the null terminators.
96
Module Level Changes in the Property Palette

q
Savepoint Mode = False
Notice that there is NO illustration of this for Forms 5 & Developer 2000 V2.
97
Block Level Changes in the Property Palette

q
Enforce Primary Key = Yes (Default is No.) Key Mode = Nonupdatable (Default is Automatic.) Locking Mode = Delayed (Default is Automatic.)
Values of Automatic work without changes.
98
Item Level Changes in the Property Palette

q
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, if using ODBC.
99
You, Developer 2000/Forms, & Rdb

q
q q
Improvements in the software have made the Rdb connection more transparent. There is still value in defining table keys. There is still value in understanding the issues.
100
A User View
To understand how to use Developer 2000, you must understand what your application user will see from the choices that you make. Developer 2000 provides significant functionality by default. q Pulls in metadata q Establishes defaults for

q q
labels item characteristics spacing canvases windows,
Provides a form for connecting to the database. More ...

101
Default Menus and Toolbar
q q
Pull-down menus Toolbar
More ...
102
Querying
q q q q
Enter Query Execute Query Count Hits Cancel
Specifying the query criteria: q Any subset of the fields available q Exact matches q Wildcarding q <, >
Query retrieval by groups of rows

103
Help
Choosing Help on the default Help menu displays the property palette information on the item selected.
104
Hot Keys
Choosing Keys on the Help menu displays this form. Notice q F1 is Help q F7 is Enter Query q F8 is Execute Query q You can scroll for more.
105
Printing
q
Since many forms are wider than tall, printing in landscape mode is usually best. D2000 defaults to portrait.
If you use this feature well, it seems like a free report.
106
Summary
q q
Forms is a powerful multiplier of your work. Forms does some things by default.
Help for you with the metadata. Connecting to the database. Pull-down menus. Toolbar. Querying. Help. Hot Keys. Printing. More
Forms is an excellent tool for prototyping or JAD (Joint Application Development).

107
Standards and Inheritance

This section introduces how an application developer can use modern software engineer techniques from within an Oracle Developer application.
q q q q q q
Property classes (domains) Visual Attributes Program Units Object Libraries Property Classes vs. Object Libraries Templates
108
Component Software
q
Baby Steps
Create generic functionality Gradually refine functionality as needed for applications Maintenance made easier
Application
Refine
Level 2 Level 1 Level 1
Level 2 Level 1
Refine
109
Building Blocks for Software Development
Standards (Property Classes)
Interface (Visual Attributes)
Logic (Program Units)
Easy to Use, Maintainable Application

110
Standards: Property Classes Defined

q
A property class is a first generation Developer 2000 building block for application development.
Property classes allow for some level of standardization of a Forms application A property class is an entity that allows common items to have properties set automatically as well as custom event triggers automatically associated with the appropriate item Property classes are very similar to Oracle Rdb domains ID code name date money date/time code text summary money comment and others ...
111
Examples:
Example of a Property Class (Dates)

q
Format Masking
MM/DD/YYYY MM/DD/YYYY HH:MI:SS DD-MON-YYYY etc
q q
Handling the NULL date (17-NOV-1858) Date Range Searches
112
Visual Attributes
q
q q
Color, font, and other visual properties that could be assigned to various objects Allows the interface to have a standard look and feel Examples:
Current record highlighting in a multi-record block Highlight the current item in a form Company Logo Etc.
113
Program Units
q
Program units are PL/SQL procedures and functions that are encompassed in a form Used for tasks that could potentially occur multiple times in a single form Example:
JCCs GET_ID functionality Override Developers default assembly of the query Population of default values when creating a new record Etc.
114
Menus and Toolbars

Oracle Developer supports the creation of MDI menus and toolbars
Menus and Toolbars once created can be referenced and included by every form Dynamically enable and disable functionality during runtime Reference form specific code via Developer built-in DO_KEY
q
The DO_KEY statement causes the corresponding form events to fire

This ensures that the event code path can be called and executed the same way each time Requires less code maintenance by creating/developing/debugging once
Example: DO_KEY ( EXECUTE_QUERY );

Statement will fire the KEY trigger which triggers the Query events
115
Property Class Module

If using a pre-Developer 2.x release JCC recommends: q Create a separate module for property classes q Copy the property classes from this module to other form modules, as a subclass q Ensure all form modules reference the same property class module Enforces a single point of code maintenance (software building block)
116
Object Library Definition

q
The Object Library is a Developer 2000 second generation mechanism used to store objects that can be referenced by forms Objects can include:
Blocks and Items Property Classes Visual Attributes Program Units Etc.
The Object Library is a means to allow for the reuse of commonly used components Places development standards in a single location
117
Benefits of Object Libraries

q
Object Libraries are opened automatically when you start the Forms Designer
Makes objects immediately accessible
Multiple Object libraries may be associated with a form

One for company standards One for work group standards One for personal standards A single object can reference only one entry in a particular Object Library so Object Libraries cannot be in conflict with one another.
Do not need to drag and drop all objects into your active form to make objects available
118
Property Class Module vs. Object Libraries

q
Property Classes
Can contain property classes, but not all items in pre-Developer 2.x could be subclassed (Program units) Must have Property Class module open in order to drag in and drop property classes to make them available to a form Only way to implement inheritance pre-Developer 2000 Release 2.0
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 implements inheritance (linked during compilation)
119
Developer Templates
q
A template is a starting form that you use to build other forms. It is not a true inheritance structure but can utilize inheritance structures like items from the Object Library. Templates may include (either referenced or nonreferenced):
Toolbars Program Units Canvases Attached Libraries Etc.
Templates are a great way of getting through the muck.

120
When to Use Inheritance Structures

q
Property Classes
These structures store property settings for forms, blocks and items
q
Templates
This structure provides a starting point for form creation
q
Use Property Classes whenever possible for similar items
Object Libraries
This structure is a common storage location for all generic items.
q
JCC recommends using a template that references an object library since templates themselves are not a true inheritance structure
Use Object Libraries to store items such as Property Classes, toolbars, menus, etc.
121
Graphical View of Inheritance Structures

Appication Form Object Library
Property Classes Toolbars Menus Attached Libraries Etc. Referenced Prop. Classes Referenced Toolbars Referenced Menus Referenced Attached Lib. Form Specific Items Form Specific Functions Etc.
References
122
Summary
q
This section provided an overview of the concepts of application development and mapped software engineering terminology into Developer functionality Developer has the hooks to allow for flexible and maintainable applications By using the inheritance structures, JCC has found standards and functionality easier to develop, maintain and implement.
123
Developer Intermediate Topics

Developer features that you will want to explore include: q Master-detail relationships q List of Values (LoV) q Special item types
Flags Icon buttons
q q q q q q
Radio buttons Stacked canvases Alert boxes PL/SQL Triggers (forms triggers) Creating your own toolbar or menus
124
Advanced Topics
Teaching the Application to Sing
Additional Topics
q q q
Exception Handling Stored Procedures Elaboration of morning topics

Transaction control & locking Others
126
Exceptions
q
Unexpected or abnormal result of an operation

Divide by zero Invalid data type conversion Data entered does not match format mask No rows returned by a query No changes to save
Exceptions can be raised by:

SQL PL/SQL Calls to user-named subprograms
127
Developer Exceptions
q
Oracle has several pre-defined, named exceptions

CURSOR_ALREADY_OPEN DUP_VAL_ON_INDEX INVALID_CURSOR PROGRAM_ERROR etc - see the PL/SQL Users Guide and Reference for a complete list
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
128
How Does Developer/Forms Let You Know An Exception Has Occurred?

q
Default exception handling in Forms is to display a message

Validation exceptions also disallow forward progress More severe exceptions can cause a rollback
Exceptions are first raised in the begin-end block where the exception occurs, then higher-level begin-end block, etc.
E.g. Begin begin begin <exception occurs> end; 1 end; 2 end; 3
129
How Can You Handle Expected Exceptions?

q
Exception clause
begin <executable statement> exception when <named exception> then <executable statements> when <named exception> then <executable statements> o o o when other then <executable statement> end;
130
How Can You Filter Noise Exceptions?

q
What is a noise exception?

Any exception that D2K raises that you do not care about - in our case:
q q
n records saved No records to save
On-Message trigger
Create a trigger at the form level that filters messages you do not care about
:System.Message_level
This system variable represents what severity level of messages should be suppressed by the default exception reporting
131
On-Message Trigger
q
On-Message
/* Built-in: ERROR_CODE,ERROR_TEXT,ERROR_TYPE ** Trigger: On-Message */ DECLARE errnum NUMBER := ERROR_CODE; errtxt VARCHAR2(80) := ERROR_TEXT; errtyp VARCHAR2(3) := ERROR_TYPE; BEGIN IF errnum = 40400 and errtyp = FRM THEN -- This is that stupid "Transaction complete: XXX records applied and saved" message. Null; ELSIF errnum = 40405 and errtyp = FRM THEN -- This is that stupid "No changes to apply" message. Null; ELSIF errnum = 0 THEN -- This is that stupid non-message ("-0:") message. Null; ELSE /* ** Print the Normal Message that would have appeared */ Message(errtyp||-||TO_CHAR(errnum)||: ||errtxt|| on ||:system.trigger_item); END IF; end;
132
:System.Message_level
q
declare save_message_level char(2); begin save_message_level := :system.message_level; :system.message_level := 10; -- Ignore 0, 5, 10 select x into :block.item from y where z = 2; :system.message_level := save_message_level; end; Note: Exceptions are still raised, only reporting to the user is suppressed. You should use this one carefully!
133
Recording Client Exceptions

q
Why record exceptions?

User: I just got an error. IS: What was the error? User: It said something about converting IS: What? What screen are you on? User: Screen X IS What were you doing? User Trying to open a new account. o o o Any questions?
134

q q
Problem: Need to record client exceptions Problem: Need to be able to access the exception data without having access to the machine Problem: Need to capture exceptions even when developers forget to implement exception handling 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
135

q
Comc.record_exception
This is a library (COMC) procedure which calls a database stored procedure. The database stored procedure writes information to a log file.
q
This will be described in more detail in the next section, aptly named Stored Procedures
On-Error trigger
Create a trigger at the form level that logs exceptions
136
On-Error Trigger
q
On-Error
/* ** Built-in: ERROR_CODE,ERROR_TEXT,ERROR_TYPE ** Example: Reword certain FRM error messages by checking ** the Error_Code in an ON-ERROR trigger ** Trigger: On-Error */ DECLARE errnum 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;
137
Stored Procedures
q
Procedures stored within the database are valuable for many reasons
Single source of complex update code Security Revision control Reduction of network traffic (client/server) Accessed from multiple divergent clients
They also have a down side

No return values (no native interface for D2K to return values) Rdb stored procedures have poor exception handling/reporting (it does, however, meet the SQL standards) Configuration management !?!?
138
What We Will Discuss

q q q q
How D2K calls a stored procedure Calling an Rdb Stored Procedure Example We will not discuss configuration management of stored procedures
139
How D2K Calls A Stored Procedure

q
The traditional method for calling a stored procedure from D2K is a simple, in-line call: begin procedure_to_call(); end;
Works for Oracle 7/8 procedure/data sources
140
Calling An Rdb Stored Procedure

q
The first implementation of SQL*Net for Rdb did not include stored procedure support We needed to use stored procedure calls to allow multiple platforms access to the same code Necessity is the mother of invention
Benjamin Franklin
Use Forms_DDL calls

Forms_DDL(procedure_to_call()); DDL means Data Definition Language
141
Forms_DDL
q
Upside
Allows us to make stored procedure calls today Interface is not TOO hokey
Downside
Dynamically compiled and executed on server Numeric and Date parameters must be converted to text, then back to native data types A work-around for this could be to use temporary tables to pass data between client and server Exception handling becomes more complex
142
Example - Exception Reporting Routine

q q
Problem: Capture client messages on the server Problem: Must be able to record events outside of the context of a transaction Answer: Use a stored procedure that does no database work
Short compilation and execution time Outside of transaction contexts Messages are logged on the server and can be culled on a frequent basis
143
Exception Reporting
q
Client side Forms_DDL(call comc_record_event( || name_in(system.current_form) || ~ || event_text || ~ || name_in(system.current_datetime) || ));
144
Exception Reporting
q
Server Side trace trim(:text_string) || ~ || trim(session_user) || ~ || cast(cast(current_timestamp as timestamp(2)) as char(22));
145
Results
q q
We began using this approach in the fall. We now have 10,000 - 15,000 lines of stored procedure code. We are able to write stored procedures that provide a single source for
VMS Developer anything else
146
Now The Good News

q
SQL*Net for Rdb version (next) is due out soon and reportedly supports the same native interface for stored procedures as Oracle 7/8
147
Transaction Control & Locking

q
Developer uses Read Write transactions

Implication lock conflict
SQL services for Rdb can be configured for Read Committed

Index locks remain until the scan has completed.
Additional levels of control are possible and may be required for your application. Things to consider include
timeouts nulls commits rollbacks cursors
148
JCCs Latest Move on Transaction Control

q
For each new instance of a form

rollback the existing R/O transaction start a new R/O transaction use the WHEN_NEW_FORM_INSTANCE forms trigger
For a database write

rollback the existing R/O transaction start a R/W transaction use the PRE_COMMIT forms trigger
For the commit

commit the R/W transaction with the POST_DATABASE_COMMIT forms trigger start a R/O transaction with the POST_FORMS_COMMIT forms trigger
149
Aside on How the Transaction Model Changed

q q
Standardization is the key. Action to change the entire model

one developer well over 200 forms modules 5 minutes by adding the forms triggers to the property class in the object library.
150
Additional Brief Topics
Slides from the morning presentation
Some of the Topics to Consider

q q q q q
Prototyping Standards Multiform Applications Configuration Management Automated Builds
152
Prototyping
q
With windows and Developer

prototyping is easy most of the default decisions that are built-in are useful your own standards are also quickly added with domains support for JAD (Joint Application Development) projects, or other ways of involving users, is robust prototyping of individual forms can be the basis of what you will use in production
Beyond prototyping
requires defining standards developing ways to handle the particular challenges of your application
153
Standards
q
Important
Ease of generating forms can cause chaos. Relying on industry standards minimizes training. Standards increase usability.
Readily implemented
Use Developer features: property classes, object libraries, etc. Use Developer defaults, unless ...
Goal of the prototyping explorations

Sloppy prototyping leads to chaos Lack of early user involvement leads to chaos Good prototyping leads to coherent standards
Apply to everything
154
Multiform Applications
q
Applications with one form module

Frequently used for examples Frequently used for small applications Some shops use multiple single form applications
Advantages of multiform applications

Partition development Support logical application flow Enhance flexibility Can share information across forms Amortize database connect
155
Configuration Management
q
You need to take the same care that you do with main frame applications. Our project consists of
5 or more developers working with Developer/Forms almost 300 modules
We use MicroSofts Visual Source Safe

to provide a library of all the modules
q q q q
forms icons DLLs common libraries
to ensure that we arent all working at cross purposes

156
Automated Builds
q
Batch-mode builds require

Oracle command line method No programmatic alterations of the forms For each form
q q q
attach to the database compile the form unattach
Automated builds with the Forms API

Single program control Mass changes without opening each form by hand One database attach Requires less than 20% of the time that batch mode requires in the best of circumstances
157
Other Issues and Answers

q q q q
Data Models at Variance with User Views Access Control Auditing Transaction Control & Locking
158
New Appreciation for Views

q
Requirements may suggest views.

Your users may think of a subset of the data that is inconsistent with database tables or normalization. Interfacing with legacy applications may require views. Developer doesnt tolerate 31 character names.
q q
Worse yet, ODBC doesnt tolerate 30 character names. If you are fond of long names, you will need views.
Developer is very easy to use when working with a single table or view.
Sophisticated query options are automatically included. All of the fields that you need are pulled in easily.
Pulling in data from several tables can be done more efficiently with views.
159
This form lets the user query on fields from the account, consumer, site, and meter tables. The form is based on a view and response is very fast. Updates are not allowed on this form, but the buttons at the bottom lead to forms that do support updates to the underlying tables.
160
Access Control
q q q
Views Roles 3 SQL Services levels

Process started under some VMS account SQL Service Rdb Database
Client
VMS
Requests Access
Authenticates as a VMS user (Session User)
Authorized to use this service (System User)
DBA grants access via ACLs
161
Auditing
q q q q q q q
Database triggers Audit table Form on table Changes highlighted Reference information, as required User acceptance Example
162
Audit Form Example
163
Where Do YOU Start?

q q q
Legacy application Developer defaults Other?
164
Legacy Applications
q
Copying a legacy application can produce torturous results. Most legacy applications do not include Developers event driven nature. Prototyping with a good tool frees you to
try a different approach present it to the user quickly throw it away, if you need to try something else
Adopting an utterly different style can free you and your users to think about what needs to be done. Stepping back and thinking simplistically can produce simply obvious results.
165
Developer Defaults
q
Advantages of built-in defaults

Provides a starting point Many are well chosen
Disadvantages of built-in defaults

Have changed between releases May not meet your needs
Building your own defaults

Use the standardization tools Avoid unnecessary changes from
q q
Oracle Developer standards Industry standards
166
Additional Remarks
What? We dont have four more days!
Deployment
q
Developers
Paradigm shift Group efforts Intoxicating speed Testing an event driven application
Users
Change is threatening User involvement
q q
Can help Requires a training period
Side-step competition with legacy applications Include humor

168
Rdb Specific Issues

q
The original set

The differences are dwindling. You can use Developer features to apply certain characteristics uniformly and meet the needs.
Stored procedures
Fake it.
Legacy applications
Can you write a COBOL application in Developer? Do you want to?!
Do we those of us with Rdb demand more?

Big Fast Mission critical Accurate
Manageable Predictable
169
Possible Additional Advantages to YOU, the Experienced Rdb User

q
You can learn how to embrace PC technology.

Disadvantage: You arent in Kansas any more and the Wicked Witch is unpredictable.
The vendor is the same as your database vendor.

This has meant on-going improvements in the way the two work together.
Developer can be a significant step toward flexibility and independence.
170
Questions?
Cheryl P. Jalbert Jeffrey S. Jalbert Keith W. Hare Thomas H. Musson Jeffrey S. Haidet Phone (740)587-0157 Web: www.jcc.com List Server: RdbD2K
To subscribe to the list server:
Send mail to majordomo@JCC.com. Include subscribe RdbD2K in the body of your message.
cheryl@jcc.com jeff@jcc.com keith@jcc.com tom@jcc.com jeffh@jcc.com
171
Questions?
172
Questions?
173
174

Breaking Out of The Box Oracle Forms

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Breaking Out of The Box Oracle Forms

Uploaded by

Copyright:

Available Formats

Breaking Out of the Box Oracle Developer/Forms for Experienced Rdb Developers

JCC Consulting, Inc. Granville OH 43023

EOUG: Hints and Kinks

Rdb Forum: Breaking Out of the Box

Rdb Forum: Discussion / Q & A

Rdb Forum: Demos ?

Configurations and Choices

Software Pieces and Parts Design Choices

New Ways with Terminals

Thin Clients on the Web

Configuration for Some Sessions

Background for Your Choices

What are your requirements? What are your resources?

Dumb Terminals as Your Choice

Dumb Terminals as Your Choice

Your application may be better suited to terminal styles

Client/Server Choices Five Tier Model

Translating Oracles New Names

Oracle Developer 2000 V2.x

Software Pieces and Parts

Data Transport Mechanism

Production Systems Prerequisite Software On Client

Other Software Pieces and Parts

Another Example Form

Data is erased here for non-disclosure reasons.

and Another Form ...

Integrated from Another Technology

Developing Forms -The Basics & Default Functionality

Getting Started Developing Forms

Open the Forms Builder

Open the Form Builder

Examine the new front piece provided by Oracle.

Choose a starting point.

What You See First

Module, Block, Canvas, Window

Well discuss these topics in this section.

Components: Modules and Blocks

Components: Canvases and Windows

Your Tools: Tools Menu

Your Tools: Object Navigator

Your Tools: Properties Palette

Your Tools: Layout Editor

Developers Primary Tools

The Developers Tools in an Example

Examining the Object Navigator

Closeup of the Object Navigator

Close-up of the Property Palette

Close-up of the Layout Editor

the title decorative frame (blue rectangle)

Using the Object Navigator to Add a Block

Using the Wizards

Recommendation: Use the Data Block Wizard.

Creating a Block Based on a Table

Form for Choosing the Table

Press Browse to see the list of tables and views

Or type in the name.

Connecting to the Database

Browsing the Metadata

Rdb Specifics for Browsing the Metadata

Select Other users, as well as Current user.

Select Views, if you need those, too.

Selecting Your Table or View