Re: V2.3 -> V3 Trigger conversion

Steven P. Muench (smuench_at_oracle.com) wrote:
> GRAHAM -- I'm pleased to communicate that your information is
> INCORRECT. We are committed to maintaining our unrivalled
> reputation for portability and upward compatibility. Let me
> set the record straight:
 

> Oracle Forms 4.0:
 

> --------------------------------------------
> (*) Fully supports existing syntax for 2.3-style
> triggers.
> --------------------------------------------
 

> Of course we have not *enhanced* the old trigger-step
> macro language to embody the hundreds of new commands
> that are available in PL/SQL-Style triggers, but all
> existing code works as is.
 

> --------------------------------------------
> (*) Provides an upgrade utility that converts your form
> definitions from Forms 2.0, 2.3, and/or 3.0 directly
> to the new file format for an Oracle Forms module.
> --------------------------------------------
 

> It does not physically change, massage, or otherwise
> interpret your trigger code (be it 2.3-Style or
> PL/SQL). It merely changes file format and maps old
> trigger names onto new trigger names -- without
> changing the applications functionality of course! An
> example is that your KEY-STARTUP trigger will now be
> named WHEN-NEW-FORM-INSTANCE to conform to our new,
> more intuitive trigger naming, however the moment in
> time when the trigger fires is the same as previously
> and your code is unchanged, so you have nothing to
> worry.
 

> --------------------------------------------
> (*) Provides an upgrade utility (the same one as above)
> that converts your SQL*Menu 5.0 Menu application
> definitions into Oracle Forms 4.0 menu modules.
> --------------------------------------------
 

> Unlike for forms, we do not directly support the
> upgrading of menu definitions from SQL*Menu 4.1, only
> from SQL*Menu 5.0.
 

> --------------------------------------------
> (*) Allows the coexistence of triggers written in
> 2.3-Style and PL/SQL in the same application
> --------------------------------------------
 

> Similar to Forms 3.0, you can convert some 2.3-Style
> triggers to PL/SQL if you desire (to eliminate SELECT
> FROM DUAL for numerical calculations, for example)
> but you need not convert all of them. That is, "if
> ain't not broken, you don't necessarily have to fix
> it"
 

> Of course, we recommend any *new* development take place
> using the PL/SQL-style triggers as PL/SQL is a more robust
> programming language with type-checking, flow control,
> exception handling, etc. Access to Oracle7 stored procedures
> is only available using PL/SQL, as well as the hundreds of
> new commands added to make developing GUI database apps
> easier.
 

> There are 3rd-party products which can *translate* (which I
> use rather than the word "upgrade" or "convert") your
> 2.3-style triggers into an equivalent PL/SQL-style trigger.
> But this is not strictly necessary to make your applications
> run in the later version of the Forms product. They are not
> without their place, but my point is that "translation" of
> your 2.3-style triggers is not forced upon you by Oracle.
 

> Hope this clears things up.
 

> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Steve Muench Email: smuench_at_oracle.com
> Forms Development
> Product Manager
Received on Mon Aug 02 1993 - 15:00:15 CEST