Re: Forms 3 to 4.5

From: Subramanian.R.V <suburv_at_kumaran.com>
Date: 1998/01/28
Message-ID: <01bd2c05$4acf4c40$1cef3dcf_at_suburv.kumaran.com>#1/1


Hi,

There are quite a few issues to be considered when migrating an Forms3.0 application
to GUI using Forms 4.5. There are some issues given below.

  1. renaming the old pl/sql package procedures to the new ones. -- Very important issue for upgrading Ex. BLOCK_CHARACTERSTIC to GET_BLOCK_PROPERTY.
  2. Introducing GUI Items , alerts,enhancing visual appearence viz fonts, colours.
  3. Mouse enabling -- A truly GUI characterstic. Keep in mind that mouse does not fire any key-trigger there by failing to fire any validations / checks that are in the key-triggers.
  4. And there are more.....

And about character/GUI migration there are good number of issues/trade off you need to consider before starting.

We , at , Kumaran are specialists in this area having migrated more than 500+ customers to GUI /character modes
world wide and have successfully converted in all platforms that oracle forms4.5 supports.

For More technical question's or concerns , contact Subramanian.R.V (subu) at 416-626-1332 x149.
E-mail : suburv_at_kumaran.com

For general / non-technical reasons please contact Paul Essery at 416-626-1332 x 116.
E-mail : paule_at_kumaran.com

Or use our Toll Free Number 1-800-KUMARAN. (1-800-586 2726) .

Please feel free to contact us and we will be very happy to provide you with all the information / whitepapers
you will need on this issue.

Regards,
Subramanian.R.V.(SUBU).
Kumaran systems Inc.
suburv_at_kumaran.com

David <lautech_at_darkstar.com.au> wrote in article <34CF477F.ED105124_at_darkstar.com.au>...
> Help...
> What are the main steps (and major pitfalls) of converting a Forms 3
> application (on Unix) to Forms 4.5 in a Win95/Unix Client Server
> environment? Also, what are the major differences between converting to
> 4.5 but staying in character mode on Unix, or going completely to GUI
> and Client Server?
> Thanks.
>
>
Received on Wed Jan 28 1998 - 00:00:00 CET

Original text of this message